Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop

This WebDNA talk-list message is from

2010

It keeps the original formatting. numero = 105618
interpreted = N
texte = Ken, i am not sure if you are using [replace] or [replacefounditems]. Do =not forget [replacefounditems] is much faster than the old technique of =nesting a [replace] context inside a [founditems] context.- chrisOn Jul 18, 2010, at 23:24, Kenneth Grome wrote:>> Did you check if the [replace] tag actually writes to disk?>=20> My tests confirm that replace will NOT write to disk, so that's not =the cause of the slowdown. =20>=20> I'm disappointed that my first coding approach was so slow that it was =essentially unworkable. I didn't have any idea that it would take more =than a fraction of a second to do a set of 9 replaces. But there were =two searches before the 9 replaces, and the db's were not tiny, so one =or both of these factors was apparently causing each set to taking 2-3 =seconds to complete.>=20> Now I'm re-structuring my code to try an approach that might be =faster.=20>=20> Sincerely,> Kenneth Grome>=20>=20>=20> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us Associated Messages, from the most recent to the oldest:

Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (christophe.billiottet@webdna.us 2010)
Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (christophe.billiottet@webdna.us 2010)
Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (christophe.billiottet@webdna.us 2010)
Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (christophe.billiottet@webdna.us 2010)
Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (christophe.billiottet@webdna.us 2010)
Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)
Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop (christophe.billiottet@webdna.us 2010)
[WebDNA] CORRECTION: 60% failure rate using replace in a loop (Kenneth Grome 2010)

Ken, i am not sure if you are using [replace] or [replacefounditems]. Do =not forget [replacefounditems] is much faster than the old technique of =nesting a [replace] context inside a [founditems] context.- chrisOn Jul 18, 2010, at 23:24, Kenneth Grome wrote:>> Did you check if the [replace] tag actually writes to disk?>=20> My tests confirm that replace will NOT write to disk, so that's not =the cause of the slowdown. =20>=20> I'm disappointed that my first coding approach was so slow that it was =essentially unworkable. I didn't have any idea that it would take more =than a fraction of a second to do a set of 9 replaces. But there were =two searches before the 9 replaces, and the db's were not tiny, so one =or both of these factors was apparently causing each set to taking 2-3 =seconds to complete.>=20> Now I'm re-structuring my code to try an approach that might be =faster.=20>=20> Sincerely,> Kenneth Grome>=20>=20>=20> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us christophe.billiottet@webdna.us

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] CORRECTION: 60% failure rate using replace in a loop

2010

Top Articles:

Related Readings: