Re: Page Views Database

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 59585
interpreted = N
texte = Allen Frye wrote: > > But if I set up an append context to record a page view every time a > page gets accessed/refreshed, will I get into performance issues with > the page loading or with people accessing other webDNA pages? I do that on most of my sites, and it doesn't seem to affect the server's performance at all. After all it's just a very simple add-database-entry routine, fairly minor compared to many opther things we ask WebDNA to do. In case anybody's interested, here's the code snippet I use: [APPEND db={databasename}.db] DATO=[DATE]&KL=[TIME]&SIDE=[THISURL]&IP=[IPADDRESS]&BROWSER=[BROWSERNAME]&REF=[REFERRER] [/APPEND] Of course, you'll also need to upload an empty db file with the appropriate headers. > We get > over a million hits a month, so I'm looking at at least a million > records a month in a page views table. > > Will I have to set up some scripts to flush out the page views table > regularly or can I just let it continue to get bigger and bigger? Well, the site I *don't* dare use this makeshift log on, is the one that gets visit numbers of that magnitude. ;-) I do download and clear the logs on an irregular basis. Never hit the roof yet but I've never let them run up to more than 25 000 entries before clearing. With my system that means about 3.7 megabytes. As far as WebDNA is concerned this is just another database with the same limitations and possibilities as other databases. It all depends on how much and what data you log and of course how much available RAM the server has. Usually you can expect WebDNA to handle at least 50-100 MB databases without any problems. *If* the log file gets too big for WebDNA to handle, the only thing that should happen is that it'll stop adding new entries to the base. That means the logging will stop of course, but it shouldn't affect anything else at all - except your error logs might start filling up instead. > > Or should I not try to use webDNA at all for this, and instead find a > way to use the server log file? Just answer this question: ¿Can the regular server log provide you with the information you need? *If yes: no need to bother with an additional system. *If no: go for it! I started my WebDNA based logs because the server I used for those site didn't have any log I could access at all. After that was sorted out I just kept them going partly because I'd gotten used to them, partly because they give me a more detailed picture, but mostly because they're already there and don't seem to do any harm. Frank Nordberg http://www.musicaviva.com (that's the one without the WebDNA logging) 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 http://www.website-helper.com (and a few more I can't remember at the moment) ------------------------------------------------------------- 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:

    
  1. Re: Page Views Database ( Frank Nordberg 2004)
  2. Page Views Database ( "Allen Frye" 2004)
Allen Frye wrote: > > But if I set up an append context to record a page view every time a > page gets accessed/refreshed, will I get into performance issues with > the page loading or with people accessing other webDNA pages? I do that on most of my sites, and it doesn't seem to affect the server's performance at all. After all it's just a very simple add-database-entry routine, fairly minor compared to many opther things we ask WebDNA to do. In case anybody's interested, here's the code snippet I use: [APPEND db={databasename}.db] DATO=[date]&KL=[time]&SIDE=[thisurl]&IP=[ipaddress]&BROWSER=[browsername]&REF=[referrer] [/APPEND] Of course, you'll also need to upload an empty db file with the appropriate headers. > We get > over a million hits a month, so I'm looking at at least a million > records a month in a page views table. > > Will I have to set up some scripts to flush out the page views table > regularly or can I just let it continue to get bigger and bigger? Well, the site I *don't* dare use this makeshift log on, is the one that gets visit numbers of that magnitude. ;-) I do download and clear the logs on an irregular basis. Never hit the roof yet but I've never let them run up to more than 25 000 entries before clearing. With my system that means about 3.7 megabytes. As far as WebDNA is concerned this is just another database with the same limitations and possibilities as other databases. It all depends on how much and what data you log and of course how much available RAM the server has. Usually you can expect WebDNA to handle at least 50-100 MB databases without any problems. *If* the log file gets too big for WebDNA to handle, the only thing that should happen is that it'll stop adding new entries to the base. That means the logging will stop of course, but it shouldn't affect anything else at all - except your error logs might start filling up instead. > > Or should I not try to use webDNA at all for this, and instead find a > way to use the server log file? Just answer this question: ¿Can the regular server log provide you with the information you need? *If yes: no need to bother with an additional system. *If no: go for it! I started my WebDNA based logs because the server I used for those site didn't have any log I could access at all. After that was sorted out I just kept them going partly because I'd gotten used to them, partly because they give me a more detailed picture, but mostly because they're already there and don't seem to do any harm. Frank Nordberg http://www.musicaviva.com (that's the one without the WebDNA logging) 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 http://www.website-helper.com (and a few more I can't remember at the moment) ------------------------------------------------------------- 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:

customer info (2001) Serial Number Question (1997) WCS Newbie question (1997) Re:no template caching (1997) [convertchars] limits (1998) Location of Browser Info.txt file (1997) Scoping rules in WebDNA 4.0 (2000) Using [detete] (1998) FINAL: STILL not starting on bootup (2002) Setting up shop (1997) Changes to [ReturnRaw] in 3.0 (1998) [WebDNA] Announcing the new features for the next WebDNA version (2015) security (1997) [WebDNA] Quick Grep question (2009) too many nested tags ... (1997) [WebDNA] Testing..... (2015) send mail problem? (1997) WebCat NT v. Mac (1997) Looking up two prices in database? (1997) [WebDNA] Installing Windows CICADA under IIS7/2008 Server Enterprise 64bit (2009)