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 = 101639
interpreted = N
texte = David Bastedo wrote: > I stream through the same pipe and can handle up to 6mb a second - > which I have come close to, but not quite attained. The max I have hit > in the last week is 5.5. Pushing that close to the bandwidth limit is never a good idea. This may well be one cause of the problems but perhaps not the only one. --- Rob wrote: > Which to me means that under normal conditions, low load, your lookups > are working fine, and everything functions normally. If it was a > problem in the coding, you would also see it in low load conditions as > well... yes/no? Not necessarily. An actual bug in the code would probably show up regardless but if it's a case of too complex a code for the server to handle, the scale of the problem would increase with the load. One "problem" with WebDNA is that it's a bit too useful sometimes. It's so tempting to keep adding another little script and yet another little script and... --- Kenneth Grome wrote: > How many webdna hits are you getting per minute or second? That's a very important question although of course it also depends on the complexity of the code and the capacity of the server. A very rough guide: + Less than 10 hits pr. minute: Something's really wrong if you have problems. + 10-100 hits pr. minute: Should work fine unless the code is very complex and/or the server is old and slow. + 100-500 hits pr. minute: Basic WebDNA functionality should work fine. Serious power required for advanced stuff. + 500-1000 hits pr. minute: Time to seriously consider code optimisation and perhaps a faster server. + More than 1000 hits pr. minute: You might want to consider a server cluster. --- Ken's list of optimisation tips is a very good one (thanks Ken!) Here are a few more: + Make sure you have enough *physical* RAM (virtual memory doesn't count) to run the software *and* cache all the templates and databases. This is by far the most important point. Nothing slows the server down more than reading from and writing to the harddisc. + If you use temporary databases, keep them as simple as possible: e.g. just a a list of reference numbers pointing to a permanent database rather than all the data needed. + Consider splitting large databases into smaller ones. But be careful: do this the wrong way and you end up increasing the load rather than reducing it. + Consider storing large chunks of text as text files rather than in databases and use [Include] commands to fetch them. (Another method that may backfire so be careful.) Frank Nordberg http://www.musicaviva.com http://stores.ebay.com/Nordbergs-Music-Store?refid=store http://www.abc-notation.com http://www.online-guitarist.com http://www.gitar-siden.com http://www.tablatvre.com http://www.mandolin-player.com http://www.blues-harmonica.com http://www.irish-banjo.com http://www.blues-banjo.com http://www.folk-banjo.com http://www.roarogfrank.com
Associated Messages, from the most recent to the oldest:
David Bastedo wrote: > I stream through the same pipe and can handle up to 6mb a second - > which I have come close to, but not quite attained. The max I have hit > in the last week is 5.5. Pushing that close to the bandwidth limit is never a good idea. This may well be one cause of the problems but perhaps not the only one. --- Rob wrote: > Which to me means that under normal conditions, low load, your lookups > are working fine, and everything functions normally. If it was a > problem in the coding, you would also see it in low load conditions as > well... yes/no? Not necessarily. An actual bug in the code would probably show up regardless but if it's a case of too complex a code for the server to handle, the scale of the problem would increase with the load. One "problem" with WebDNA is that it's a bit too useful sometimes. It's so tempting to keep adding another little script and yet another little script and... --- Kenneth Grome wrote: > How many webdna hits are you getting per minute or second? That's a very important question although of course it also depends on the complexity of the code and the capacity of the server. A very rough guide: + Less than 10 hits pr. minute: Something's really wrong if you have problems. + 10-100 hits pr. minute: Should work fine unless the code is very complex and/or the server is old and slow. + 100-500 hits pr. minute: Basic WebDNA functionality should work fine. Serious power required for advanced stuff. + 500-1000 hits pr. minute: Time to seriously consider code optimisation and perhaps a faster server. + More than 1000 hits pr. minute: You might want to consider a server cluster. --- Ken's list of optimisation tips is a very good one (thanks Ken!) Here are a few more: + Make sure you have enough *physical* RAM (virtual memory doesn't count) to run the software *and* cache all the templates and databases. This is by far the most important point. Nothing slows the server down more than reading from and writing to the harddisc. + If you use temporary databases, keep them as simple as possible: e.g. just a a list of reference numbers pointing to a permanent database rather than all the data needed. + Consider splitting large databases into smaller ones. But be careful: do this the wrong way and you end up increasing the load rather than reducing it. + Consider storing large chunks of text as text files rather than in databases and use
[include] commands to fetch them. (Another method that may backfire so be careful.) Frank Nordberg http://www.musicaviva.com http://stores.ebay.com/Nordbergs-Music-Store?refid=store http://www.abc-notation.com http://www.online-guitarist.com http://www.gitar-siden.com http://www.tablatvre.com http://www.mandolin-player.com http://www.blues-harmonica.com http://www.irish-banjo.com http://www.blues-banjo.com http://www.folk-banjo.com http://www.roarogfrank.com
Frank Nordberg
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:
More Applescript (1997)
Multiple catalog databases and showcart (1997)
Secure server question (1997)
Searching for all records (1998)
searching within same page (2000)
WebDNA DHTML Newsticker 1.01 released (2003)
Quick Question (1997)
-REPOST- WebCat 3 & Aliases (2000)
Problems with WebDNA-Talk list (1998)
Shownext Tricks (2000)
grep / [middle] help (2003)
writing db to disk (1997)
OK, here goes... (1997)
New to WebDNA.. Dreamweaver Extensions? (2005)
Country & Ship-to address & other fields ? (1997)
[WebDNA] API- continued - bit.ly statistics (2011)
unable to launch acgi in WebCat (1997)
Re[2]: WebCatalog on Linux (2000)
Modtime bug? (2002)
flushdatabases (1997)