Slow [spawn]

This WebDNA talk-list message is from

2003

It keeps the original formatting. numero = 49008
interpreted = N
texte = Here's a spawn context that's towards the top of a template[spawn] [include includes/ordernumfixer.inc][/spawn]ordernumfixer.inc looks like:[search db=orders.db&neorderdatedata=[blank]&asorderdatesort=1&asordertimesort=2 ][founditems] [replace db=orders.db&eqordernamedatarq=[ordername]]ordernum=[index][/replace][/founditems][/search]This is on an admin template that shows unfilled orders. The included webdna is used to auto-renumber the items in the db because staff may delete a record for various reasons (duplicate order, etc).orders.db has about 3000 records, 75 fields, and uses about 2.3 MB of RAM on a box with 512 MB of RAM. When the [spawn] is commented out, the elapsed time for the page to be processed by WebDNA is 3 seconds, and the page renders quickly. When the spawn is included, the elapsed time is 14 seconds, and the page renders as slow as a dog.What is the reason it takes so long to render? Is it because the spawned WebDNA is operating on the db, and locks it somehow so it's not available until the spawned WebDNA is finished with it?Regards,-Will--Will StarckNovaDerm Skincare Sciencehttp://www.novaderm.comwjs@novaderm.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:

Re: Slow [spawn] (Glenn Busbin 2003)
Re: Slow [spawn] (WJ Starck 2003)
Re: Slow [spawn] (Charles Kline 2003)
Slow [spawn] (WJ Starck 2003)

Here's a spawn context that's towards the top of a template[spawn] [include includes/ordernumfixer.inc][/spawn]ordernumfixer.inc looks like:[search db=orders.db&neorderdatedata=[blank]&asorderdatesort=1&asordertimesort=2 ][founditems] [replace db=orders.db&eqordernamedatarq=[ordername]]ordernum=[index][/replace][/founditems][/search]This is on an admin template that shows unfilled orders. The included webdna is used to auto-renumber the items in the db because staff may delete a record for various reasons (duplicate order, etc).orders.db has about 3000 records, 75 fields, and uses about 2.3 MB of RAM on a box with 512 MB of RAM. When the [spawn] is commented out, the elapsed time for the page to be processed by WebDNA is 3 seconds, and the page renders quickly. When the spawn is included, the elapsed time is 14 seconds, and the page renders as slow as a dog.What is the reason it takes so long to render? Is it because the spawned WebDNA is operating on the db, and locks it somehow so it's not available until the spawned WebDNA is finished with it?Regards,-Will--Will StarckNovaDerm Skincare Sciencehttp://www.novaderm.comwjs@novaderm.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/ WJ Starck

DOWNLOAD WEBDNA NOW!

Slow [spawn]

2003

Top Articles:

Related Readings: