Workstations
Full disks, too little memory for the software in use, dozens of programs loading at start-up, and antivirus scanning a project folder that ought to be excluded.
Picture an architecture practice in Kranj with fifteen staff. Projects sit on a network drive in the office, and opening a large model takes several minutes. Anyone working from home avoids big files over the VPN altogether, copying them to a laptop in the morning and forgetting to put them back at night. On Wednesday afternoons, when everybody starts plotting drawings ahead of the client meeting, the network drive slows so badly that some applications crash. The usual first suggestion is a new server or faster disks. Before buying anything, it is worth finding out where the time actually goes. The answer is often surprisingly mundane: a switch running at 100 Mbit/s because of a damaged cable, antivirus scanning every file that opens, or a backup job that kicks off at two in the afternoon. We measure what happens during the slowest hours, pinpoint the bottleneck and remove it remotely. New hardware only comes up once free configuration changes are used up, and only if we can show the benefit in numbers. As we do not sell equipment, we have no reason to talk you into something bigger.
Slowness nearly always has one main cause and a few contributing ones. We work through the layers from the user's screen down to the database and web server.
Full disks, too little memory for the software in use, dozens of programs loading at start-up, and antivirus scanning a project folder that ought to be excluded.
Disks rebuilding after a failure, a poorly configured SMB setup, folders holding hundreds of thousands of tiny files, and a server weighed down by backups in the middle of the working day.
Ports negotiating the wrong speed, faulty cables, overloaded Wi-Fi access points, and traffic that should stay local travelling over the link between sites instead.
Limits of the free SQL Server Express edition, missing or fragmented indexes, tables nobody has maintained, and a client version that does not match the server.
Applications reaching an office database over VPN as though they were in the same room. Often it is better to run the program in the office or the cloud and send the user just the screen image.
OneDrive attempting to sync a hundred gigabytes of projects onto every laptop, and SharePoint libraries that have outgrown the recommended limits.
Slow server response, uncompressed images, plugins firing dozens of queries per page, and stock synchronisation scheduled right at peak traffic.
Diagnosis takes one to two weeks. Fixes are rolled out gradually, in slots that cause the least disruption.
For a week staff note in a simple form what was slow and when. Precise timestamps are worth more than a general “everything is slow”.
We time typical tasks such as opening a project or issuing an invoice, while an agent records load on the server, disks and network.
The log and the measurements are overlaid. You get a list of causes with evidence and a recommendation on where to begin.
Approved changes are applied remotely and the same measurements repeated. A month later we check the improvement has held.
The free edition has quiet limits. Plenty of business applications are installed on the free SQL Server Express in smaller deployments. That edition caps each database at 10 GB and restricts how much memory and processor power it can use. As the company grows, the database creeps towards the cap and the software slows down however powerful the server is. Checking database size and edition takes a few minutes and can spare you a purchase that would not have helped.
Sometimes, though often not. If measurements show the server is constantly maxed out, you receive a technical specification and buy from a supplier of your choice. Physical installation is done by your staff or a local contractor, while we migrate data and configure everything remotely.
Diagnosis and fixes are billed at €50 per hour plus VAT against an estimate sent beforehand. We do not promise percentage gains before measuring, but after the fixes you see the difference in seconds.
Possibly in part. Measurements let the conversation with the vendor rest on data rather than guesswork. Changes to the application are made by the vendor; we look after the server, database and network.
Yes. We check the VPN, home broadband and how the application reaches its data. It often helps to run the program in the office or cloud and send only the screen home. Home-working rules such as equipment and expense reimbursement belong in a written arrangement under ZDR-1.
Yes. We measure Core Web Vitals and server response time, review caching, images and plugins, and show what your hosting cannot cope with. We only suggest switching provider if the measurements back it up.
Describe one specific task that holds your team up and how long it takes. Within one working day we will suggest where to start measuring.
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
No town by that name here. Check the letters, or settle for the nearest larger place. Our engineers work only over the internet, so Kočevje and Koper get precisely the same treatment.