Comments for Normation Blog

Comment on Barcamp Rudder 2.4.0 – Portes ouvertes by Jean

Jean — Tue, 21 Feb 2012 19:49:42 +0000

Je vais essayer de passer mardi 28.
Je vais bien trouver une ou deux améliorations pour Rudder, même si vous persistez à avancer dans les demandes que je vous envoie

Jean

Comment on Optimizing Eclipse performances by [Eclipse] optimize eclipse | SoftBlog

[Eclipse] optimize eclipse | SoftBlog — Thu, 22 Dec 2011 17:47:00 +0000

[...] http://blog.normation.com/2010/05/24/optimizing-eclipse-performances/ This entry was posted in C/C++, Java, Linux by Jay. Bookmark the permalink. [...]

Comment on Optimizing Eclipse performances by +NT

+NT — Sat, 05 Nov 2011 18:06:40 +0000

Thanks, sped up my eclipse by 3-4 times!

Comment on Why we use Cfengine: memory footprint by Which open source configuration management tool should I use? | Vertical Sysadmin

Thu, 15 Sep 2011 17:11:05 +0000

[...] Why we use Cfengine: memory footprint [...]

Comment on Optimizing Eclipse performances by Michael Horne

Michael Horne — Wed, 17 Aug 2011 10:57:38 +0000

Bless you. Eclipse was driving me up the wall.

Comment on Optimizing Eclipse performances by Drupad Panchal

Drupad Panchal — Thu, 30 Jun 2011 16:15:55 +0000

-XX:CompileThreshold indicates the number of times a method must be executed before compiling it. The default value set by JVM is 10k.
If you specify a value like 5, then a certain method will be compiled to native code after 5 executions. This, however is a desired operation by many of us at the same time the your default Code Cache is set to 32m so now it fills up quickly. Once your Code cache is full, things start to appear slow because no more methods are being compiled anymore. Everythings interpreted (everyone knows how slow this can be). So do not blindly set this value to ’5′, instead try to fine-tune this parameter according to your usage. Try to set this value at -XX:CompileThreshold=1000 and go up or down, depending on your application and its usage, to improve the performance. For large/massive applications you can also increase the default size of your Code Cache with this setting -XX:ReservedCodeCacheSize=32m
change from 32m to say.. 64m (if you have tons of memory to spare)

Comment on Cfengine 3.1.5 is nearly out, what can we expect from it? by Ben

Ben — Tue, 24 May 2011 11:58:11 +0000

Good example of parsestringarray.
This is exceedingly useful!

Comment on Cfengine 3.1.5 is nearly out, what can we expect from it? by Nicolas C.

Nicolas C. — Tue, 17 May 2011 12:42:40 +0000

The packaged version are now available, Alex.

Comment on Optimizing Eclipse performances by James Cuzella

James Cuzella — Fri, 13 May 2011 19:29:29 +0000

-XX:CompileThreshold=5 gave me some terribly slow performance on Ubuntu 10.04.

Getting rid of this option alone cut my Eclipse startup time down to 17 seconds from >1 min! Please see:

http://www.java.net/node/671068

Comment on Cfengine 3.1.5 is nearly out, what can we expect from it? by Alex

Alex — Fri, 06 May 2011 21:22:19 +0000

Any idea when they will release a packaged version of 3.1.5? I came in on 3.1.4 and have had a lot of problems supposedly fixed, and don’t know how soon they create packages…