All company databases (DBs) that have exceeded 1 GB in size at least once are automatically moved to the Large DB server. Users have constantly requested: “We want more stable application performance; we are willing to pay more just for better stability.” Therefore, we are separating some DBs to the Large DB server — this will allow for faster performance for everyone. We have been additionally focusing on overall speed issues and are continuously making general improvements that affect all DBs on all servers. Large DBs (LDBs) clearly highlight bottlenecks in the system and provide direction for improvement. Why are LDBs moved to the Large DB server?Such companies account for up to 0.2% of all companies and consume an exceptionally large amount of server resources:the sizes of generated temporary files alone are measured in TBs;queries are performed 50-1,000 times slower;DB performance metrics show that the load differs by millions of times (compared to a regular DB) and LDBs consume a significant portion of CPU and RAM;data in certain modules is calculated in hundreds of thousands or millions of records.It is obvious that LDBs cannot be maintained using simple pricing designed for 99.8%+ of users. Therefore, Site.pro, at its own discretion, prioritizes companies whose databases are heavily loaded and carries out the transfer process to the LDB server.Why do LDBs slow down after 1 GB, while everything is fast and cheap for Google, GoogleDrive, or YouTube?The main problem is that these are live data — they cannot be put into a “cache”.When data is in Google or Youtube systems, it is prepared in advance. It is ranked once and then displayed many times.Accounting data does not work this way. When an accountant changes 1 digit, the annual report must change immediately. And there cannot be any yesterday's copy (“cache”) here. Our tests with different DB sizes and different servers showed that 1 GB is the critical point after which a DB starts working slower and requires additional attention. 1 GB is just one of the indicators considered when making a decision to move a DB to another server.What does DB size depend on? DB size depends on the number of operations and the amount of data. Roughly (since data types are different, and one record often creates entries in several tables, and they are very different), one GB of a single DB contains about 1,000,000 DB records.Do the data stored additionally in the Storage affect the DB size? Photos and files uploaded to Site.pro are uploaded to a separate file storage. These files have no effect on the DB and are not subject to additional charges. The storage itself costs relatively little, so clients are not charged for it.What is my DB size, do I have to order the Large DB server service?You do not need to worry about this. Companies that exceed 800 MB will see a separate notification on the company dashboard (that “Your company's database size is approaching the 1GB limit, and upon exceeding the limit, the database will be automatically moved to the Large DB server”).You can see company DB sizes in your Account under the “Companies and users” section.Who has to pay for the Large DB server, the accounting company or the client?In our opinion, such DBs should be paid for by the client, not by the accounting company. We see the following reasons for this:Data remains with the client and does not need to be transferred after the contract expires;During a GDPR audit, the Client may have fewer questions;There is no need to change the accounting company's service price and include additional costs;The client understands that they are paying for resources separately.Is it expensive? How much does a separate server cost elsewhere?As far as we know, if you have your own accounting software purchased somewhere and do not have server costs for it, then the server costs for a 1GB+ database would be as follows (e.g., Dedikuoti.lt prices excluding VAT); Site.pro uses Amazon RDS servers, which are significantly more expensive and stable (we have verified this empirically).Two servers (analogue to Amazon RDS), e.g., “Windows8”: 31.18€ x2 = 62.36€;Backups: 1€;If, for example, 5 people connect, you will need 5 separate “Remote Desktop Access CALs” licenses (the price depends on many parameters). We could not find the price;1-2 DevOps expert hours per month depending on response speed: 70€ x 2 = 140€;Accounting software updates and DevOps costs to install them. Price is negotiable;Installation, 1-4 DevOps hours. Price: 70€ x 4 = 280€.Will my database work faster on the Large DB server?We performed measurements with the resources of at least 15 different servers and did not notice significantly faster performance when a DB is over 1 GB in size.If a server does not have enough resources, it is obvious that it starts to work slower. But when there are more than enough resources — DB performance does not accelerate. Everything depends on the amount of data in the company's DB.Why does my DB size fluctuate? LDB size can fluctuate depending on how often you work with the DB. DB sizes are systematically optimized and reduced (without losing data).