Re: Closing databases
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 46726
interpreted = N
texte = Glenn Busbin wrote: > >>How does it determine which ones are immediately needed? >> > > > It..uh...Well, you see....uh...When it sees...uh...Oh. Just like the way it ranks search results then? ;-)Sorry to bother you all with this, but it's rather important to me. (Well, to be honest it isn't. I can just check the log files tomorrow morning, but I'm just too impatient ;-)Ignoring for now the fact that we gave WebCatalog a big chunk of extra memory just a few months ago to keep exactly this from happening, here's a scenario:All in all there are about 60-70 database files.There's this big one (coupl'a meagas) that's being accessed once a second or so - even more during peak hours.There are a couple of medium sized ones (200 KB-3 MB), some are accessed as often as the big ones, others much rarer.There are a couple of really small ones (just a few kilos) that are accessed - say about once a minute each on average.So there's this big monster. Bigger than all the others put together. Needed almost as often than all the others put together. Really slow to reload. Is that the one WebCatalog will close?Frank ------------------------------------------------------------- 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:
Glenn Busbin wrote: > >>How does it determine which ones are immediately needed? >> > > > It..uh...Well, you see....uh...When it sees...uh...Oh. Just like the way it ranks search results then? ;-)Sorry to bother you all with this, but it's rather important to me. (Well, to be honest it isn't. I can just check the log files tomorrow morning, but I'm just too impatient ;-)Ignoring for now the fact that we gave WebCatalog a big chunk of extra memory just a few months ago to keep exactly this from happening, here's a scenario:All in all there are about 60-70 database files.There's this big one (coupl'a meagas) that's being accessed once a second or so - even more during peak hours.There are a couple of medium sized ones (200 KB-3 MB), some are accessed as often as the big ones, others much rarer.There are a couple of really small ones (just a few kilos) that are accessed - say about once a minute each on average.So there's this big monster. Bigger than all the others put together. Needed almost as often than all the others put together. Really slow to reload. Is that the one WebCatalog will close?Frank ------------------------------------------------------------- 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/
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:
[dos] command (1997)
Re[2]: Wierd problem with 3.08 WIN Version (2000)
customizing the color of user's pages (1997)
using showpage and showcart commands (1996)
[WebDNA] Internal [ipaddress] ? (2009)
MacWEEK article help needed (1996)
Nested tags count question (1997)
Forcing a NEWCART (1997)
AppleScript question (1997)
shipping costs (1997)
WC 2.0 frames feature (1997)
Nesting WebDNA in JavaScript (2003)
Can you do this??? and other stuff (1997)
Error Lob.db records error message not name (1997)
The Form authentication trick (2000)
Cart ID (1999)
[protect admin] (1997)
Date Sorting (1997)
update on wn searching (1997)
SMSI FTP (2002)