Performance Quickr 8.1 Bugs

  • 01 Apr, 2009

Fez parte da instalação que fiz no Datacenter migrar um Quickr 8.0 para a versão 8.1. Instalei tudo corretamente mas a performance do servidor ficou muito ruim.
Pesquisando sobre o problema encontrei a solução:  Quickr 8.1 com Domino 8.0.1 tem um problema com cache, basta migrar a versão do Domino 8.0.2 que o problema realmente desapararece.
A referência do problema e solução pode ser vista no [http://www.quickrblog.com/](http://platao.plansis.com.br/blogkenio.nsf/dx/<a href=http://www.quickrblog.com//><span style=)“ title=“http://www.quickrblog.com/”> Quickr Blog de Stuart McIntyre

Related Posts

Bypass IBM Web Content Manager Caching

  • 21 Mar, 2017

If you have Basic or Advanced caching enabled in IBM® Web Content Manager, then Web Content Manager caches content artifacts independently of the cache settings that you configured for the Web Content Viewer portlet. To bypass the caching that is set in Web Content Manager, select the option Bypass Web Content Manager Caching. This setting applies to content artifacts that are rendered in this Web Content Viewer portlet only. This feature was added on CF11 for Portal/WCM

Bypass IBM Web Content Manager CachingRead More

How to enable gzip compression on IBM HTTP Server

  • 06 Feb, 2017

One of the tuning activities is to turn on GZIP compression for HTTP requests. This tuning can save lots of network traffic and your page will load in a short time. Just put the lines bellow on the httpd.conf and restart the server LoadModule deflate\module modules/mod\deflate.so LoadModule headers\module modules/mod\headers.so Only the specified MIME types will be compressed. AddOutputFilterByType DEFLATE application/atom+xml AddOutputFilterByType DEFLATE application/atomcat+xml AddOutputFilterByType DEFLATE application/javascript AddOutputFilterByType DEFLATE application/json AddOutputFilterByType DEFLATE application/octet-stream AddOutputFilterByType DEFLATE application/x-javascript

How to enable gzip compression on IBM HTTP ServerRead More

Performance problems with Full Text Indexer

  • 17 Jun, 2015

Last week two clustered servers are facing performance problems. The cpu was very high for 2 hours and the disk queue above 5,48. During the problem the command set config UPDATE\NO\FULLTEXT=1 was issued and the cpu and disk queue decrease To schedule the full text index i use the this TN(http://www-01.ibm.com/support/docview.wss?uid=swg21571557)

Performance problems with Full Text IndexerRead More