Re: [WebDNA] Not even sure what to ask for help on. . . :(
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 101637
interpreted = N
texte = =46rom what I recall, nested searches are faster than 2-3=20 lookups, so you should probably use nested searches in this=20 situation. =20 > I am wondering if I should replace all the tables=20 > in the site with a temp .db.=20 I would use a permanent db if I were you, here's why ... Both temporary db's and tables are available only to the=20 thread that creates them, but permanent db's are available=20 to all threads. In other words, it's far more efficient to=20 use just one db for everyone than to use one temp db or=20 table for each visitor. Here are some other suggestions: Always use static pages wherever possible, even if you have=20 to write a special webdna script to generate them. Always use a non-webdna suffix on your static pages so=20 webdna never has to process them -- and so the http server=20 can cache them itself. Display dynamic webdna code in static pages via iframes, and=20 keep the html in those iframe pages to a minimum so webdna=20 doesn't have to parse any more html than necessary. Move all images, movies, pdf's, sound files, etc. off the=20 webdna server and onto a generic file server. Set your webdna preferences to: Always interpret WebDNA [xxx] tags on all pages (so webdna=20 doesn't have to waste time trying to find a HAS_WEBDNA_TAGS=20 string before it starts working) Cache Templates (so webdna can interpret them faster) Check for template modifications every 3600 seconds (so=20 webdna doesn't have to check every 2 seconds for updated=20 templates) Only commit databases to disk when instructed (so webdna=20 doesn't have to write to disk unless you tell it to -- and=20 don't tell it to write to disk any more than necessary=20 either) Safe Write for database - No (so webdna can write the=20 RAM-cached data to the original db file on disk rather than=20 writing to a new copy of that file and then replacing the=20 original with the new copy every time) =2D-------------- Naturally some things you do to speed up webdna may put your=20 data at risk, but if you have backups it may not be that=20 important. How many webdna hits are you getting per minute or second? Sincerely, Ken Grome
Associated Messages, from the most recent to the oldest:
=46rom what I recall, nested searches are faster than 2-3=20 lookups, so you should probably use nested searches in this=20 situation. =20 > I am wondering if I should replace all the tables=20 > in the site with a temp .db.=20 I would use a permanent db if I were you, here's why ... Both temporary db's and tables are available only to the=20 thread that creates them, but permanent db's are available=20 to all threads. In other words, it's far more efficient to=20 use just one db for everyone than to use one temp db or=20 table for each visitor. Here are some other suggestions: Always use static pages wherever possible, even if you have=20 to write a special webdna script to generate them. Always use a non-webdna suffix on your static pages so=20 webdna never has to process them -- and so the http server=20 can cache them itself. Display dynamic webdna code in static pages via iframes, and=20 keep the html in those iframe pages to a minimum so webdna=20 doesn't have to parse any more html than necessary. Move all images, movies, pdf's, sound files, etc. off the=20 webdna server and onto a generic file server. Set your webdna preferences to: Always interpret WebDNA [xxx] tags on all pages (so webdna=20 doesn't have to waste time trying to find a HAS_WEBDNA_TAGS=20 string before it starts working) Cache Templates (so webdna can interpret them faster) Check for template modifications every 3600 seconds (so=20 webdna doesn't have to check every 2 seconds for updated=20 templates) Only commit databases to disk when instructed (so webdna=20 doesn't have to write to disk unless you tell it to -- and=20 don't tell it to write to disk any more than necessary=20 either) Safe Write for database - No (so webdna can write the=20 RAM-cached data to the original db file on disk rather than=20 writing to a new copy of that file and then replacing the=20 original with the new copy every time) =2D-------------- Naturally some things you do to speed up webdna may put your=20 data at risk, but if you have backups it may not be that=20 important. How many webdna hits are you getting per minute or second? Sincerely, Ken Grome
Kenneth Grome
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:
Review comparison by PC Magazine: Open for On-line Business (1997)
Re:Emailer and encryption (1997)
Conveting Characters to Graphics (1997)
Practice runs ? (1997)
WebDNA Developer Edition - Host config problem (2003)
Bug Report, maybe (1997)
[SearchString] usage (1997)
WebCat2 several catalogs? (1997)
Why won't this work (2005)
Adding discount to cart (2000)
Help Encrypt/Decrypt eMail (2003)
bug in listwords? (1998)
WC1.6 to WC2 date formatting -FIXED! (1997)
Further tests with the infamous shipCost (1997)
How To question on setting up downloads (1997)
Enhancement Request for WebCatalog-NT (1996)
WebCat2 beta 11 - new prefs ... (1997)
E-mail Attachments (1997)
HELP! 10K hits per hour for pages that no longer exist! (2000)
Lambada for Macintosh is Here! (1996)