Re: make updates in a temporary database
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 57659
interpreted = N
texte = Sounds like a disk contention issue. webcatalog (oops, WebDNA) loves to save stuff to disk after every little change, make 10,000 changes, that's 10,000 writes to the HD of a 2 meg file. (hopefully this has changed a little in the last few years) 1) TURN OFF AUTOSAVE in the admin area. You're now on your own on all of your templates to save changes to disk after you've modified databases, but since everything happens in ram with no disk activity (until you call for it) things will go much faster. 2) get rid of nested searches and nested search/replaces where possible. There are smarter ways of finding and updating info that are more efficient. Streamline your code. 3) NO, flushdatabases would not be a better choice, it would be a significantly worse choice as you would then suffer a penalty of reloading the databases from the disk to access them again. stick with commitdatabases. 4) if none of the above work for you: buy a better server. 10K scsi HDs in a RAID do make a difference if your code accesses it a lot. Brian B. Burton On May 5, 2004, at 7:46 AM, Lester wrote: > [commitdatabase db=products.db] > is used in my admin when I update the database after > making a change to it. > > would [flushdatabases]be a better choice here? > > > > I also was looking in the webdna preferences > and saw that there is a line: > > Seconds to wait for busy database = 20 > > the explaination of (from admin help): > Prevents database deadlock by only waiting a certain > amount of time before "giving up" on an exclusive lock > of a database. > > > would changing this item help any ? > > > > > > > --- Lester
wrote: >> 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/ > > > > > > __________________________________ > 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/
Associated Messages, from the most recent to the oldest:
Sounds like a disk contention issue. webcatalog (oops, WebDNA) loves to save stuff to disk after every little change, make 10,000 changes, that's 10,000 writes to the HD of a 2 meg file. (hopefully this has changed a little in the last few years) 1) TURN OFF AUTOSAVE in the admin area. You're now on your own on all of your templates to save changes to disk after you've modified databases, but since everything happens in ram with no disk activity (until you call for it) things will go much faster. 2) get rid of nested searches and nested search/replaces where possible. There are smarter ways of finding and updating info that are more efficient. Streamline your code. 3) NO, flushdatabases would not be a better choice, it would be a significantly worse choice as you would then suffer a penalty of reloading the databases from the disk to access them again. stick with commitdatabases. 4) if none of the above work for you: buy a better server. 10K scsi HDs in a RAID do make a difference if your code accesses it a lot. Brian B. Burton On May 5, 2004, at 7:46 AM, Lester wrote: > [commitdatabase db=products.db] > is used in my admin when I update the database after > making a change to it. > > would [flushdatabases]be a better choice here? > > > > I also was looking in the webdna preferences > and saw that there is a line: > > Seconds to wait for busy database = 20 > > the explaination of (from admin help): > Prevents database deadlock by only waiting a certain > amount of time before "giving up" on an exclusive lock > of a database. > > > would changing this item help any ? > > > > > > > --- Lester wrote: >> 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/ > > > > > > __________________________________ > 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/
Brian B. Burton
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:
WCS Newbie question (1997)
webmerchant (2000)
WebCommerce: Folder organization ? (1997)
[WriteFile] problems (1997)
WebDNA Developer Resource Center (2002)
[WebDNA] An actual attempt to get WebDNA and MAMP Pro to work - (2018)
Search: Is this possible? (2005)
Linux Orderfile Error (2002)
Execute Applescript (1997)
Searching for words equal to A or equal to B (1999)
back button loses cart (2000)
Emailer Chokes on bad address (1997)
still having shipCost.db Problem (1997)
Quitting WebMerchant ? (1997)
If Empty ? (1997)
WebCatalog 4.0.1b1 is now available (2000)
WebCatalog can't find database (1997)
creating a ShipCosts database (1997)
[INCLUDE] Limitations (1998)
Need relative path explanation (1997)