[opencms-dev] Bad performances problem with queries in the database

[m.lambin at crelan.be]

Thanks for your answers, but i think it's not the solution.

There's my configuration:
        <flexcache>
            <cache-enabled>true</cache-enabled>
            <cache-offline>false</cache-offline>
            <maxcachebytes>8000000</maxcachebytes>
            <avgcachebytes>6000000</avgcachebytes>
            <maxentrybytes>400000</maxentrybytes>
            <maxkeys>10000</maxkeys>
        </flexcache>


And there are the datas in Opencms Flexcache Administration
Variations in Flex Cache: 204
Keys in Flex Cache: 33
Max. size of all variations: 8000000 bytes
Avg. size of all variations: 6000000 bytes
Cur. size of all variations: 804560 bytes

So, my cache properties are configured the same way as your example (
uri;element;params=(print,accessible);timeout=60).










                                                                           
             "Joe Desbonnet"                                               
             <jdesbonnet at gmail                                             
             .com>                                                      To 
             Sent by:                  "The OpenCms mailing list"          
             opencms-dev-bounc         <opencms-dev at opencms.org>           
             es at opencms.org                                             cc 
                                                                           
                                                                   Subject 
             28/06/2006 15:09          Re: [opencms-dev] Bad performances  
                                       problem with queries in the         
                                       database                            
             Please respond to                                             
              joe at galway.net;                                              
             Please respond to                                             
                The OpenCms                                                
               mailing list                                                
             <opencms-dev at open                                             
                 cms.org>                                                  
                                                                           
                                                                           




I forgot to ask: have you set a reasonable Flexcache size? If the web
site "working set" is greater than the max allowed cache size, the
cache will fail badly in something like a  JMeter stress test.


On 6/28/06, Joe Desbonnet <jdesbonnet at gmail.com> wrote:
> It's my understanding that hits from Flexcache are served from memory
> with zero DB activity.
> What is your template's cache property exactly?
>

_______________________________________________
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 email and any attached files are confidential and may be legally privileged.If you are not the intended recipient, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited.  If you have received this transmission in error please notify the sender immediately and then delete this email.Email transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.  The sender therefore is in no way liable for any errors or omissions in the content of this message, which may arise as a result of email transmission. If verification is required, please request a hard copy.
Please bear in mind that the content of any email leaving and entering the recipient network 
will be verified against viruses, spam and unsuitable content in accordance with the recipient 
policies and regulations.  Halted messages will therefore be destroyed without any further 
notice.