Performance update
Tuesday morning once again saw the e-conomic application crawling to a near-halt for a couple of hours. This was quickly identified as being due to a subtle issue with a recently-introduced feature, which was subsequently optimized, thus eliminating the immediate issue.
However, prior to this, we have had several similar slowdowns over the past couple of months. We have identified the more general culprit to be an underlying storage system for our database back-end. In very simple terms, the disk speeds cannot keep up with certain functionalities. However, remedying this isn’t simply a matter of ‘adding faster disks’ – there’s quite a lot of careful planning involved as well. Right now, several people at both e-conomic and our hosting partner are working on this.
At the same time, we are of course doing everything we can to reduce the effects of this problem in the immediate term. This involves a lot of old-fashioned code optimizing – which has already been applied to several functions. Additionally, some specific functionalities have been identified to use a disproportionate amount of resources compared to the share of customers using it. For these functionalities, we may impose restrictions requiring these customers to e.g. filter reports more narrowly. In more extreme cases, we may choose to completely disable access to certain ‘heavy’ functionality for a short while, as we work on optimizing it.
We will of course keep you updated on both immediate, short and longer-term improvements and solutions to this.
Posted by Christian Estrup

[...] Onsdag oplevede vi en ekstraordinær stor belastning grundet et uheldigt sammenfald af flaskehalse. Disse flaskehalse gjorde at data hobede sig op og systemet blev gradvist langsomt. Vi har iværksat følgende. På den korte bane intensiverer vi overvågningen af systemet. Vi skal hurtigere slå ned på processer, der trækker uforholdsmæssigt mange ressourcer ud af systemet. På den længere bane skal vi foretage flere ting herunder ændre opsætning, forbedre kode mm. Vores teknikere har lavet et indlæg på vores tekniske blog herom. Teknisk interesserede vil også … [...]
[...] vi har vidtagit de åtgärder vi kan för att det inte ska upprepas. Läs gärna mer om detta på vår teknikblogg (länken är på [...]