[opencms-dev] Flexcache counters

Wed Mar 24 11:11:12 CET 2010

I'm sorry if I offended you with what I said. It was meant constructive and should only raise your awareness that your proposed solution intentionally doubles every one of your requests. If that is not a potential problem for your server environment or doesn't ring bells at least, then just ignore it. ;)

Chuck, we have a similar solution running right now with OpenCms, which would basically have to an database update/insert for every request. Through buffered database writing (application bean buffer + jdbc bulk insert) every 100 requests or so this is not a performance problem at all (at least not for the database server).

Roman

________________________________

Von: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Chuck Mysak
Gesendet: Mittwoch, 24. März 2010 08:21
An: The OpenCms mailing list
Betreff: Re: [opencms-dev] Flexcache counters

Request are not bad ideas. And there are no bad ideas, only problems that appear.

The most important problem that arises is the persistence that has to happen at the request. For instance, the database that holds these values for each page that has to be updated on each request. Or the big hashtable (pages, counts) that has to be serialized and persistent between sessions. That could bring down the server performance-wise. 

Thanks,

Chuck

On Wed, Mar 17, 2010 at 6:23 AM, Tim Daschner <timd at thedoleco.com> wrote:

	those are strong words. But I take your word that those must surely be bad ideas for the world you are in. in general, a web request to your server is not exactly a bad idea. in general network is cheap and fast. again, in general, client side technology is also capable of javascript/ajax and such. so i dont see that as a bad idea in general. 

	On Mon, Mar 1, 2010 at 5:58 AM, Roman Uhlig Maxity.de <roman.uhlig at maxity.de> wrote:

		In your suggestion the Ajax is client sided, so every Ajax call creates an additional request, thus doubling the requests to your server. Bad idea.

		I'd stay pure server sided, e.g. with an application bean or something similar.

		Roman

		________________________________

		Von: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Tim Daschner
		Gesendet: Freitag, 26. Februar 2010 05:35

		An: The OpenCms mailing list
		Betreff: Re: [opencms-dev] Flexcache counters

		would an ajax call from your html to a servlet work? that servlet could count hits to your page and update the html too. just an idea.. i would say the code would be trivial too.

		On Tue, Feb 23, 2010 at 9:04 AM, Roman Uhlig Maxity.de <roman.uhlig at maxity.de> wrote:

		       > find someone who will implement  this

		       Hmmm, my planner says NO. ;)

		       But I'll put it on my open source TODO list, maybe there's an unexpected gap between projects. *hope springs eternal*

		       Roman

		       -----Ursprüngliche Nachricht-----
		       Von: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Achim Westermann

		       Gesendet: Dienstag, 23. Februar 2010 15:21

		       An: The OpenCms mailing list
		       Betreff: Re: [opencms-dev] Flexcache counters

		       Hi Roman,

		       > Tho plain storage of resource access counters in a database would not work with OpenCms pages with high load in terms of performance (1 insert per hit).

		       hmmm doubts!
		       In a clean website with optimal caching the idea is that those insers would only happen for each variation in the cache. OK after something
		       is published that will happen all over again.

		       > I.e. we've developed an application bean for that, which collects these data, processes and consolidates them and stores them as bulk data in a database. Still creates about 20 GB of data per year. ;)

		       OK, then lets add that requirement too and continue to find someone who will implement  this for the benefit of being a hero!

		       kind regards,

		       Achim

		       _______________________________________________
		       This mail is sent to you from the opencms-dev mailing list
		       To change your list options, or to unsubscribe from the list, please visit
		       http://lists.opencms.org/mailman/listinfo/opencms-dev

		       _______________________________________________
		       This mail is sent to you from the opencms-dev mailing list
		       To change your list options, or to unsubscribe from the list, please visit
		       http://lists.opencms.org/mailman/listinfo/opencms-dev

		_______________________________________________
		This mail is sent to you from the opencms-dev mailing list
		To change your list options, or to unsubscribe from the list, please visit
		http://lists.opencms.org/mailman/listinfo/opencms-dev

	_______________________________________________
	This mail is sent to you from the opencms-dev mailing list
	To change your list options, or to unsubscribe from the list, please visit
	http://lists.opencms.org/mailman/listinfo/opencms-dev