> -----Oorspronkelijk bericht----- > Van: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Namens Kees Jongenburger > Verzonden: vrijdag 12 augustus 2005 10:58 > Aan: Discussion list for developers > Onderwerp: Re: [Developers] VOTE: new project: query cache > release framework > > > > > My only worry is that the administration of all this > might be more > > > work then anticipated, both in code and execution time. > > > > what kind of administration do you mean? > I think he is talking about additional cpu work that has to > be performed in order to keep caches up 2 date and define if > a cache is still valid.
well, My first thought was to implement the current cache release stragegy as the default basic strategy. This strategy checks if the query under evaluation has nodes set for the step that corresponds to the type of the changed node. if this is so,and the number of the changed node is not one of those, the query can stay in the cache. Then i changed my mind and thought it would be better to create a nice, light, but effective set of rules as a default strategy. The reason being that some very simple rules can couse a quite dramatic decrease of cache flushes (i think). But we can allways descide to maintain the current default behavour, and offer the enhanced ruleset as a configurable option. What i would like is to postpone this decision to the testing phase, where the system will be tested under real conditions, and performance and cost can be measured (which is one of the benefits of the new system). One consideration is that the mmbase middel tire is (at least in hour setup) more easily scalable than the database tire. we can not cluster hour database, but we can loadbalace/cluster mmbase. so, if we hit the ceiling with database performance (sooo many qeries) i gladly pull some load to the application tier. ernst > _______________________________________________ > Developers mailing list > [email protected] > http://lists.mmbase.org/mailman/listinfo/developers > _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
