Following up on our last performance update, we have made a number of changes to both our hardware and software setup – working on multiple levels, such as optimizing code, tweaking our network infrastructure, updating storage, etc..

Regarding code optimization, a number of tweaks have been made. This should be particularly obvious when bulk-synchronizing data via the e-conomic API, or in general use of the Stock Management module (although said Stock Management module does still reduce the speed of a lot of operations, due to the much more complex housekeeping required).

A major change is a move of our database from traditional mechanical disks to flash (memory-based) disks. In addition to a general performance increase, this also results in much more consistent performance, thus resulting in fewer extreme peaks. This isn’t the end of our storage performance improvements, however – during the summer, we will be moving our entire setup to even faster storage.

On the database software side, we are currently looking into an update of both the database engine and operating system. However, such updates always involve a certain risk – both in terms of performance and compatibility – a risk we’re currently working hard to resolve.

Once again, a new feature, as well as some bug fixes, have found their way to the e-conomic API.

In the new features department, cash book entries – as represented by the ICashBookEntry class – now have an Employee property. This effectively allows you to add per-employee costs to projects – just like you can already add time entries.

Additionally, two annoying bugs have been fixed:

When adding lines to a subscription, an exception is no longer thrown if no Department is specified (thanks to Claus Aaberg for reporting this in our API forum).

The recently-introduced new entry type ManualDebtorInvoice – allowing you to create customer invoice entries without creating actual invoices – can now be created with the DueDate property set.

As a final note – please remember that we’re always more than interested in your comments, questions and suggestions in our API forum.