Login  Sign up

Server Optimization


1. Make sure your server specification is within the system requirements
2. Optimize your Server machine


The following information is for experienced system administrators, so please ask your IT responsible to read the document as a checklist and try ALL of the settings. 

“3GB” Switch

The 3GB switch applies mostly to sites with Windows servers with large databases and with MySQL mirroring. But it could also help smaller sites.

Description: image001 Always back up all your data before changing any settings!

“Unable to alloc 12345 bytes”

If the farmerswife server crashes with a message “unable to alloc 12345 bytes”, it is likely that the VM size for your Farmers WIFE process gets close to 2 GB (monitor this with the Virtual Bytes performance monitor counter, or check manually with Task Manager > View > Select Columns).

If this is the case, add the switch “/3GB” to your c:\boot.ini – this allows Farmers WIFE to use up to 3 GB of user-mode memory. 


[Boot Loader]



[Operating Systems]

multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows Server 2003" /fastdetect /3GB

Description: image001 boot.ini is a hidden, write-protected operating system file – be careful when editing it! Also, the “/3GB” setting may cause trouble on Windows 2000 Server Standard Edition.


Please follow this step by step guidance: Go to My Computer > Properties > Advanced > Startup and Recovery > Settings > System Start up > Edit


3 GB switch in Windows 2008 or Vista

To enable the 3GB switch on Windows Vista™:

1. Right-click Command Prompt in the Accessories program group of the Start menu. Click Run as Administrator.

2. At the command prompt, enter "bcdedit /set IncreaseUserVa 3072"

3. Restart the computer.


To disable the 3GB switch:

1. Right-click on Command Prompt in the Accessories program group of the Start menu. Click Run as Administrator.

2. At the command prompt, enter "bcdedit /deletevalue IncreaseUserVa"

3. Restart the computer.

For more information on the 3GB switch, refer to the following Microsoft MSDN article:


And see the blog:

3. Speed Test

  • To perform a “Speed Test” from your farmerswife Server simply click on the button on the Server window. There is no need to disconnect users from the Server while performing the test.


Description: SpeedTest


  • The log window shows the results and once the test is done you will be prompted to restart the server. All users connected will need to disconnect at this point.


Description: SpeedTestLog


  • If you're unsure about the result, send an email to including the log.txt from the server, (typically at C:\Program Files\farmerswife Server\system).

4. OS/Software

  • Always keep an eye on your Windows Event Log and on the Task Manager.
  • The cisvc service is a common hog on CPU and RAM. Set it to Disabled in Administrative Tools > Services > Startup Type, and also disable it on all your NTFS drives, as in this picture.  Check in Task Manager after next reboot that cicsv is indeed not running anymore. 
  • Try disabling your antivirus software for a day and see if performance improves.
  • Try setting Set Affinity to 1 on the Farmers WIFE Server process in Task Manager.



5. Database

MySQL 5 should run on a separate machine, see Hardware recommendations above.


6. Page file

System Properties > Performance Options >Virtual Memory: a typical setting for Farmers WIFE servers with large databases is

  • Initial Size = 4000 MB
  • Maximum Size = 9000 MB

You can experiment with larger “Maximum Sizes” as long as you have enough disk space. Note that there is no harm setting a big Maximum Size; it will simply allocate some more disk space. As a guideline for Maximum Size, look at Peak Commit Charge in Task Manager.

Description: image001 Please also ask your IT responsible to monitor the Windows Event Log. This often tells if something is not healthy on the hardware or OS level. Basically there should be no warnings and errors. If there are, they should be fixed immediately.


Remember to Always Keep your Hard Disk DE-FRAGMENTED!

7. Reduce your database size


  • Archiving old projects

Through the archive process, booking data gets stored outside the FW database, but the Project data remains in the database allowing you to still search for Archived Projects. This operation will decrease the size of the database and improve performance. You can restore Archived Projects easily at any time since the ‘Archive’ and ‘Restore From Archive’ procedures are done directly from the Client Application. 

Description: image001 You can only archive Closed and/or Invoiced projects, so all the 'Active' projects which are old, should be first set to 'Active: No' (please see the new47_Archiving_Manual.pdf to guide you).

  • Archiving old tasks

Tasks are Bookings NOT associated to a Project. By archiving Tasks, they will also be stored outside the database therefore reducing its size. This operation is done through the Server Application and requires that users are logged off (please see pages 10 and 11 of the new47_Archiving_Manual.pdf to guide you).

  • Delete deleted bookings

All your deleted Bookings and Binders are stored within Deleted Bookings And Binders in your Toolbox.

It is strongly recommended that when this list becomes too big and contains old bookings that will never be restored, it should be emptied.

To perform this operation go to Toolbox > Deleted Bookings And Binders > click on the arrow on top > select Delete All

Description: image001 You need the corresponding User Permission to be able to perform this operation.


8. Review other performance related server settings

9. Review performance related user settings

 Some of these tips are temporary, fast solutions in case your hardware would eventually change if not meeting the minimum requirements. Please see these server requirements at the beginning of this document. And also note that for the Client application certain minimal specs apply and depending on how this machine is being used, these changes are a pre-requisite to improving application side performance.


You might have to help your colleagues who are not as experienced users to apply these settings within their own user settings. 

  • Maximum Search Hits

  • Disable ‘Resolve Surrounding Conflicts When Bookings Change’

If enabled farmerswife will automatically change the ‘red’ coloring of a conflicting booking, after it has been resolved, for example by changing one of the conflicting bookings to ‘planning’ status.

If disabled, when resolving a conflict, the ‘red’ coloring of the conflicting booking will only change after manually confirming its status again.

Find it in Toolbox > Settings > Server Setup > Resolve Surrounding Conflicts When Bookings Change

  • Disable ‘Auto Refresh Timeline When Server State Changes’

If you disable this option, you can always update your view of the Timeline by using the ‘Refresh’ button in the bottom left corner of the Client interface, whenever you need to.

  • Reduce amount of projects shown in Long Form > Project Tree

If you have a long list of Projects in the Tree, try to reduce them. Be careful using In the 'Long Form' "Auto from Viewport / Calendar" function. If using it, use the Toolbox > Settings > Miscellaneous > Show Only Active Projects.

Did you find it helpful? Yes No