DeskNow Knowledge Base
 
      

Performance tuning

This article provides a few tip and strategies to optimize the performance of your DeskNow installation.

Tuning the database

The most important factor in DeskNow's performance is determined by the database.

With few configuration changes, the database performance can be increased considerably, providing a faster experience and allowing a server to host more accounts.

The first step in tuning your Database is to find out which database you're using - if unsure, or if DeskNow was installed by another person.

To find out which database you're using: open the C:\desknowdata\cfg\Database.cfg (/var/desknowdata/cfg/Database.cfg) file, and look at the Url parameter (NB if you find a line preceded by a #, it is commented out, and should be ignored. The file will contain only one line beginning with 'Url').

  • If the value of the Url parameter contains the word 'postgresql' , then you're using the PostgreSQL database. Most likely, you're using the default database that is included in the Windows version of DeskNow. In this case, see this article: /kb/idx/0/145/article/ .
    If your PostgreSQL database is on Linux, see this article: /kb/idx/0/061/article/ .
  • If the value of the Url parameter contains the word 'mysql' then you're using the MySQL database. In this case (both Linux and Windows), see this article: /kb/idx/0/116/article/ 
  • If the value of the Url parameter contains the word 'microsoft', then you're using MS SQL Server (2000 or 2005). Refer to the documentation of the Database for performance tuning (typically very little needs to be done)
  • If the value of the Url parameter contains the word 'mckoi', then you're using the old embedded database. We recommend migrating data to another database, that will offer much better performance. See this article: /kb/idx/9/132/article/

Reducing the amount of mail processed

Very often a lot of mail received by a mail server is spam. Even when it is correctly identified as spam, it takes up system resources to process and store these emails. With a few simple changes, the amount of spam mail that enters the processing queues can be drastically reduced.

  • consider enabling Greylisting (in Administration/Antispam). This will reject a lot of spam mail before it even enters the system.
  • consider enabling the option to immediately reject blacklisted connections (Administration/Antispam/DNSBL). This will also reduce the amount of spam mail processed.

Clustering

Consider scaling DeskNow to a cluster of two or more servers (see the Administration manual at the section 'Clustering and load balancing'). Clustering not only improves performance for systems with many users, but will also provide high-availability and redundancy, so that if one server crashes for any reason, users will still be able to use another server.

Email Article Email
Print Article Print


How helpful was this article to you?
Related Articles
article Performance tuning for MySQL database
By default MySQL is installed with very...

  April 11, 2006    Views: 21103   
article Performance tuning for PostgreSQL database (Linux)
Note: this page is for tuning PostgreSQL on...

  October 27, 2004    Views: 103467   
article Performance tuning for the embedded PostgreSQL database (Windows)
PostgreSQL can be a very fast database, but its...

  August 11, 2006    Views: 24373   



Powered by Lore :: (c)2003 Pineapple Technologies.