Re: make updates in a temporary database
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 57647
interpreted = N
texte = The slowdown in the admin side only occurs when the site has heavy access, making me think that while I'm "updating" the .db and many others are also trying to "view" that same .db, some issue of who's first occurs .. . . All is well and has always been well during periods when access to the website is not that heavy . . . The admin is made from the vers. 4.5 storebuilder code. I'll look at the code and see if I'm flushing db's --- charles kline
wrote: > I am wondering why you are seeing the slowdown. 2MB > is nothing for a > db. We make modifications to 800MB databases > regularly (using WebDNA) > and never have any problems. > > Maybe your code could be optimized?? > > - Charles > > On May 4, 2004, at 7:42 PM, Lester wrote: > > > I have a site where making to the changes during > > "peak" periods causes my admin functions to > basically > > go s-l-o-w or the admin pages freeze up it seems. > > > > Only during these peak user periods. > > > > It's not practicle to make changes during off-peak > > periods, so that can't be the solution. > > > > I'm thinking that when I'm making changes to the > > database, and people are accessing this same > database > > during this period, that's when my issue appears. > > > > It's not a large database, maybe 2 megs or so. > > > > I was thinking working on an exact duplicate of > the > > "live" database and then when changes are done > > "swapping" the worker version with the "live > version. > > > > Anyone doing something like this?? > > > > How did you approach it all codewise? > > > > > > I'm still using vers 4.5 > > > > Thanks > > > > > > > > > > > > > > __________________________________ > > Do you Yahoo!? > > Win a $20,000 Career Makeover at Yahoo! HotJobs > > > http://hotjobs.sweepstakes.yahoo.com/careermakeover > > > > > ------------------------------------------------------------- > > This message is sent to you because you are > subscribed to > > the mailing list > . > > To unsubscribe, E-mail to: > > > To switch to the DIGEST mode, E-mail to > > > > Web Archive of this list is at: > http://webdna.smithmicro.com/ > > > > > ------------------------------------------------------------- > This message is sent to you because you are > subscribed to > the mailing list > . > To unsubscribe, E-mail to: > > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/ __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
The slowdown in the admin side only occurs when the site has heavy access, making me think that while I'm "updating" the .db and many others are also trying to "view" that same .db, some issue of who's first occurs .. . . All is well and has always been well during periods when access to the website is not that heavy . . . The admin is made from the vers. 4.5 storebuilder code. I'll look at the code and see if I'm flushing db's --- charles kline wrote: > I am wondering why you are seeing the slowdown. 2MB > is nothing for a > db. We make modifications to 800MB databases > regularly (using WebDNA) > and never have any problems. > > Maybe your code could be optimized?? > > - Charles > > On May 4, 2004, at 7:42 PM, Lester wrote: > > > I have a site where making to the changes during > > "peak" periods causes my admin functions to > basically > > go s-l-o-w or the admin pages freeze up it seems. > > > > Only during these peak user periods. > > > > It's not practicle to make changes during off-peak > > periods, so that can't be the solution. > > > > I'm thinking that when I'm making changes to the > > database, and people are accessing this same > database > > during this period, that's when my issue appears. > > > > It's not a large database, maybe 2 megs or so. > > > > I was thinking working on an exact duplicate of > the > > "live" database and then when changes are done > > "swapping" the worker version with the "live > version. > > > > Anyone doing something like this?? > > > > How did you approach it all codewise? > > > > > > I'm still using vers 4.5 > > > > Thanks > > > > > > > > > > > > > > __________________________________ > > Do you Yahoo!? > > Win a $20,000 Career Makeover at Yahoo! HotJobs > > > http://hotjobs.sweepstakes.yahoo.com/careermakeover > > > > > ------------------------------------------------------------- > > This message is sent to you because you are > subscribed to > > the mailing list > . > > To unsubscribe, E-mail to: > > > To switch to the DIGEST mode, E-mail to > > > > Web Archive of this list is at: > http://webdna.smithmicro.com/ > > > > > ------------------------------------------------------------- > This message is sent to you because you are > subscribed to > the mailing list > . > To unsubscribe, E-mail to: > > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/ __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Lester
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Integrating Bar Codes with WebDNA (2006)
Link with [cart] in db field (1999)
Multiple 'Users.db' files not possible (1997)
if/then/else question - nevermind, my stupidity... (2000)
WCS Newbie question (1997)
f2 download problems (1997)
wrong authentication (1998)
Free shipping (2000)
Server Freeze (1998)
WebCatalog NT beta 18 now available (1997)
Need Sample Template - just purchased (1997)
[date] problem with %d%m%Y (1998)
WebCatalog Work (2001)
b12 cannot limit records returned and more. (1997)
Roundup function? (1997)
Error Messages Returned to User (1997)
Runnaway Trigger (2007)
Sorting by date (1997)
MetaKW tags from databases (2006)
carriage returns in data (1997)