items tagged with morespeed

This module controls the setting of the Expires HTTP header and the max-age directive of the Cache-Control HTTP header in server responses. The expiration date can set to be relative to either the time the source file was last modified, or to the time of the client access.

These HTTP headers are an instruction to the client about the document's validity and persistence. If cached, the document may be fetched from the cache rather than from the source until this time has passed. After that, the cache copy is considered "expired" and invalid, and a new copy must be obtained from the source.

How to activate mod_expires.so
# vi /etc/apache2/conf.d/mod_expires.conf

config is rough right now, but it is better than nothing,put the following in the file

LoadModule evasive20_module     /usr/lib/apache2/mod_expires.so
<IfModule mod_expires.c>
 ExpiresActive On

 ExpiresDefault "access plus 1 month"
 #ExpiresByType text/html "access plus 1 month 15 days 2 hours"
 #ExpiresByType image/gif "modification plus 1 month"
 #ExpiresByType image/png "modification plus 1 month"
 #ExpiresByType image/jpg "modification plus 1 month"
 #ExpiresByType text/css "access plus 1 month 15 days 2 hours"
 #ExpiresByType text/javascript "access plus 1 month 15 days 2 hours"
</IfModule>

You can also set the expire header by type, but it wa snot working in my case, that is why I use the ExpiresDefault directive

• Apache mod_expires references 

The acronym LAMP refers to a solution stack of software, usually free and open source software, used to run dynamic Web sites or servers. It stand for: Linux, for the operating system; Apache, the Web server; MySQL, the database management system (or database server); Perl, Python, and PHP, the programming languages.

 ab is a tool for benchmarking your Apache Hypertext Transfer Protocol (HTTP) server. It is designed to give you an impression of how your current Apache installation performs. This especially shows you how many requests per second your Apache installation is capable of serving.
Apache-utils package contains utility programs for webservers and some add-on programs useful for any webserver. These include:

• ab (Apache benchmark tool)
• Logresolve (Resolve IP addresses to hostname in logfiles)
• htpasswd (Manipulate basic authentication files)
• htdigest (Manipulate digest authentication files)
• dbmmanage (Manipulate basic authentication files in DBM format, using perl)
• htdbm (Manipulate basic authentication files in DBM format, using APR)
• rotatelogs (Periodically stop writing to a logfile and open a new one)
• split-logfile (Split a single log including multiple vhosts)
• checkgid (Checks whether the caller can setgid to the specified group)
• check_forensic (Extract mod_log_forensic output from apache log files)

This package Apache-Utils can be install through apt or YaST depending if you are using a Debian base distro or OpenSuse

We had serious performance problems with MAVEN in our environment. It seems to be a recurrent problem
for MAVEN... anyway I did came through the following changes...the 2.0.9.db1 Maven2 patch make really
Maven fly!

General settings to speed up Maven:

• More memory for Maven process, change the launcher of eclipse to set MAVEN_OPTS like this:
  -DMAVEN_OPTS="-Xms64m –Xmx128m"
• Use the latest version of Maven, but be careful of regressions! the latest as for today is 2.0.9
• There is a patch available for Maven 2.0.9, which speed up build by 40%. It is just simply day and
  night! try it, you'll love it! Basically Don Brown alter MAVEN2 2.0.9 to
  • use HTTP connection pooling !
  • use HTTP timeouts !
  • Download artifacts in parallel !
    download and read how this was done at
    http://www.jroller.com/mrdon/entry/making_maven_2_not_suck
    and his jar here http://people.apache.org/~mrdon/maven-2.0.9-SNAPSHOT-uber.jar

General settings to speed up Eclipse:

1. Use javaw.exe to start eclipse and not java.exe (more for console base program with a lot of feedback),
   while javaw.exe is more for graphical environment.
2. Aggressive JIT and double core processors should use:  
    -XX:-UseParallelGC -XX:+AggressiveOpts -XX:-UseConcMarkSweepGC -XX:+UseFastAccessorMethods
3. Give more memory, MORE MEMORY for eclipse, on a 4GB machine, these are my settings: 
   -Xms768m -Xmx1024m -XX:MaxPermSize=256m
4. Reduce the number of warning reported by eclipse per compilation unit (class), default is 100, reduce it to 10.
   It help nobody to see a workspace slowing down because of too many warning logging.
   Remove the warnings instead ;-)
5. SVN console with subversive is too verbose as default, go to eclipse preferences - Team – SVN - Console.
   Logging SVN errors should be enough.
6. Use a Defragmenter! NTFS fragment fast with so many small files in workspace, every 2 week is a good practice.
7. I am using Java 1.6u10 (BETA!) and have experience no crash till now,
   being on the edge can be costly in time through. Maven forking should benefit from the reduce java kernel
   size and bootstrap time