Re: 'page impression' techniques for banner ads
This WebDNA talk-list message is from 1999
It keeps the original formatting.
numero = 22207
interpreted = N
texte = >>How does closedatabase and commit database affect speed? If a server crashes >>and use the #1 technique then I'll lose a lot of the data. So if I add a >>commitdatabase call would that be the same as going to the disk like option >>2? > >This is a good question. I've always wondered ... > >Which is faster, committing a database to disk every time or appending a >character to a separate text file every time? I'll bet it has to do with >the size of the db compared to the size of the file, but I would love to >hear from PCS on this one too ... :) > >Since writing to a separate file auto-commits (if I may use that term in >this situation) the value as it is written to that file, using option #2 >would never require any special effort to commit the most current values to disk. > >Still, #2 would seem to be slower than adding a commitdatabase tag to the >#1 snippet. But of course, there's really no need to commit the db after >*every* page impression when using #1 either. After all, we are talking >about 'page impressions' here -- data that is not generally considered to >be extremely critical in the grand scheme of things.As I read into this (which is possibly wrong, your mileage may vary), commitdatabase only writes to disk if there is something to be written, i.e., you do 700 searches to a database, and then issue commitdatabases, and nothing will happen, because you didn't change the database. Only after doing something that modifies a database is a commitdatabase tag useful. Also, the autocommit databases setting in the WebCatalog admin should only cause WebCatalog to save changes to disk if and only if a template causes a database to change, not is you simply surf a site and perform searches. I have seen NO appreciably speed penalty leaving autocommit databases on, other then during LARGE database processing/merging actions. Brian B. Burton BOFH - Department of Redundancy Department --------------------------------------------------------------- MMT Solutions - Specializing in Online Shopping Solutions 973-808-8644 http://www.safecommerce.comAre you a Web Programmer? I am today.
Associated Messages, from the most recent to the oldest:
>>How does closedatabase and commit database affect speed? If a server crashes >>and use the #1 technique then I'll lose a lot of the data. So if I add a >>commitdatabase call would that be the same as going to the disk like option >>2? > >This is a good question. I've always wondered ... > >Which is faster, committing a database to disk every time or appending a >character to a separate text file every time? I'll bet it has to do with >the size of the db compared to the size of the file, but I would love to >hear from PCS on this one too ... :) > >Since writing to a separate file auto-commits (if I may use that term in >this situation) the value as it is written to that file, using option #2 >would never require any special effort to commit the most current values to disk. > >Still, #2 would seem to be slower than adding a commitdatabase tag to the >#1 snippet. But of course, there's really no need to commit the db after >*every* page impression when using #1 either. After all, we are talking >about 'page impressions' here -- data that is not generally considered to >be extremely critical in the grand scheme of things.As I read into this (which is possibly wrong, your mileage may vary), commitdatabase only writes to disk if there is something to be written, i.e., you do 700 searches to a database, and then issue commitdatabases, and nothing will happen, because you didn't change the database. Only after doing something that modifies a database is a commitdatabase tag useful. Also, the autocommit databases setting in the WebCatalog admin should only cause WebCatalog to save changes to disk if and only if a template causes a database to change, not is you simply surf a site and perform searches. I have seen NO appreciably speed penalty leaving autocommit databases on, other then during LARGE database processing/merging actions. Brian B. Burton BOFH - Department of Redundancy Department --------------------------------------------------------------- MMT Solutions - Specializing in Online Shopping Solutions 973-808-8644 http://www.safecommerce.comAre you a Web Programmer? I am today.
Brian B. Burton
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:
Re2: Calculating multiple shipping... (1997)
Associative lookup style? + bit more (1997)
Anyone get webdna to run on apache 2.x on osx? (2006)
File Security (1999)
More on the email templates (1997)
Tab Charactor (1997)
anyone have an automated template encrypter? (2000)
GroupField Returns (2002)
F3 crashing server (1997)
RE: Re:Signal Raised (1997)
Assigning new CART number (1997)
AppleScript question (1997)
WebCatalog 2.0 & WebDNA docs in HTML ... (1997)
[WebDNA] WebDNA Sciprt for Zipping files? (2012)
What are SMSI's upgrade policies? (2003)
The & Problem (1998)
Invisible files (2002)
WebCat, The Trend, & Consolidating... (1997)
splitting up items in a cart (1999)
Extended [ConvertChars] (1997)