Nobody Else’s Month End: What Isolation Means on Your Busiest Day
Month end, payroll day and the year-end close are when a system earns its keep. What actually competes for attention on those days, what isolation changes, and what it does not, tier by tier.
Ask a finance team when their system is slowest and they will name the same three days: month end, payroll and the year-end close. It is not because the software changes on those days. It is because everyone is asking it for the heaviest things at once.
What a busy day is made of
Most of the heavy lifting on a busy day happens out of sight, in background work the person at the screen never sees directly:
| Work | Where it runs | What you notice |
|---|---|---|
| Payslips and statements as documents | Background queue | How long before they arrive |
| Notification and statement emails | Background queue | Whether staff get them today |
| Large reports and exports | On request, then queued | How long the screen waits |
| Scheduled jobs: reminders, alerts, recurring work | Scheduler | Whether they fire on time |
On any system, the queue is first come, first served. The question isolation answers is simple: whose work is in the queue ahead of yours?
On a shared service
Everyone’s background work shares one queue. That is efficient and, most of the time, invisible: jobs are small and the queue drains quickly. On the busiest days of the month, though, a great many organizations are running payroll and closing their books at the same time, and their work and yours take turns.
Isolation does not make the work smaller. It decides whose work stands in front of yours.
On a dedicated instance
A dedicated instance has its own queue worker and its own scheduler. The only work in its queue is your organization’s. Another organization’s payroll run never lines up in front of your payslips, and another organization’s scheduled jobs never delay yours.
There is one thing to be clear about, because it is the difference between the two tiers. On the Dedicated tier your instance shares a physical server with other dedicated instances. Its queue, database and application are its own, but the machine’s processors and memory are shared with those few neighbours. On the Dedicated server tier, the machine runs your instance and nothing else, sized to your organization.
| Shared | Dedicated | Dedicated server | |
|---|---|---|---|
| Your queue holds only your work | No | Yes | Yes |
| Your scheduler runs only your jobs | No | Yes | Yes |
| The machine is yours alone | No | No | Yes |
| Capacity sized to you | No | No | Yes |
For most organizations whose busy days hurt, the queue is what they notice, and the Dedicated tier is enough. If your month end is unusually heavy, or a reviewer will ask who else is on the machine, the Dedicated server tier is the one to price. Shared or dedicated covers the rest of what changes between them.
Diagnose your busy day first
Payslips or statements arriving late on payroll day
If you see
Documents queuing.
Look at
A queue of your own: the Dedicated tier.
One large report slow at any time of the month
If you see
The report itself.
Look at
Its filters and date range, before hosting.
Everything slow on the same few days
If you see
Competing demand.
Look at
Dedicated, or Dedicated server for a heavy month end.
A reviewer asking who shares the machine
If you see
A question about hardware.
Look at
The Dedicated server tier.
Verdict
A dedicated instance gives your organization a queue and a scheduler of its own, so nobody else’s month end stands in front of yours. The Dedicated tier still shares the machine with a few other dedicated instances; the Dedicated server tier does not. Choose by what your busy day actually looks like.
What AWRA OpsHub does today
- A queue worker and scheduler that run for your instance only, on both dedicated tiers.
- Its own database and application, used by your organization alone.
- A Dedicated server tier, where the machine runs your instance and nothing else.
More we can add to your workspace
- Extra background workers for your instance, for organizations whose month end produces far more documents than most.
- The AWRA mobile app connected to your dedicated instance, alongside the web app.
Where we point you to a specialist
- We do not promise a response time for a report your filters make enormous. We will help you narrow it, and that usually does more than any hardware.
Each of these can be scoped into a dedicated-instance quote.
For a heavy month end
Where your busiest days need more than the standard instance, these are the additions we build.
More background workers
Additional workers for your instance, so large document runs finish sooner.
A machine sized to you
The Dedicated server tier, specified for your own peak rather than an average one.
The mobile app on your instance
Staff phones connecting straight to your own address.
How it works: tell us what your busiest day involves, and we return a written scope and cost.
See the dedicated instanceYour month end, and nobody else’s
A dedicated instance with its own queue and scheduler. Available to set up now.
See how it worksFrequently asked questions
Why is an ERP slow at month end?
Because many heavy tasks run at once: payslips and statements, emails, large reports and scheduled jobs. On a shared service, many organizations are doing the same on the same days.
Does a dedicated instance have its own background queue?
Yes. Its queue worker and scheduler run for that instance only, so another organization’s work never waits in front of yours.
Does the Dedicated tier share a server?
Yes, with a few other dedicated instances. Its queue, database and application are its own, but the machine’s processors and memory are shared. The Dedicated server tier gives you the machine alone.
Will a dedicated instance make every report faster?
Not necessarily. A report that is slow at any time of the month is usually about its filters and date range, and is worth narrowing before changing hosting.
