Why Server Configuration Directly Affects Tally Performance
Tally on Cloud performance is not primarily determined by the data centre's location or the provider's marketing claims — it is determined by the specific server configuration: OS version, RAM allocation, storage type, CPU allocation, and whether resources are dedicated or shared. Each specification maps directly to a measurable aspect of Tally's day-to-day performance for your users.
This guide provides specific technical recommendations for Tally cloud server configurations by user count and workload type, based on real-world performance observations from deployed environments.
Operating System — Windows Server 2022
The only correct OS for multi-user Tally cloud hosting is Windows Server 2022 (or 2019) with Remote Desktop Services configured. This is non-negotiable for multi-user setups.
Windows Server 2022 Standard edition supports unlimited virtualised instances and multiple RDS user sessions with appropriate CAL licensing. Windows 10/11 supports only one concurrent RDP session — this is a fundamental architectural constraint of those OS editions, not a configuration limitation.
M A Global Network runs Windows Server 2022 on every Tally hosting plan. Confirm "Windows Server 2019" or "Windows Server 2022" explicitly from any provider before signing anything.
RAM Allocation — The Most Critical Specification
RAM is the primary performance constraint in multi-user Tally environments. When the server runs low on available RAM, Windows begins swapping memory contents to disk — a process called paging. On NVMe SSD this is significantly slower than RAM access. The result is visible as Tally slowdown that worsens as more users connect.
| Component | RAM Required | Notes |
|---|---|---|
| Windows Server OS baseline | 4 GB minimum | Constant regardless of user count |
| Each concurrent Tally user session | 1.5 – 2 GB | Windows session + Tally process + open company file |
| TDL add-on overhead (complex TDLs) | +0.5 GB per user | Only for memory-intensive TDL tools |
| Safety headroom (recommended) | +2 GB above total | Prevents RAM ceiling under peak load |
| Concurrent Users | Minimum RAM | M A Global Network Recommended | Monthly Cost |
|---|---|---|---|
| 1–2 users | 6 GB | 6 GB | ₹700 – ₹1,400/month |
| 3 users | 9 GB | 10 GB | ₹2,100/month |
| 5 users | 12 GB | 14 GB | ₹3,500/month |
| 6 users | 13 GB | 16 GB | ₹4,200/month |
| 8 users | 18 GB | 20 GB | ₹5,600/month |
| 10 users | 22 GB | 24 GB | ₹7,000/month |
| 15 users | 32 GB | 36 GB | ₹10,500/month |
| 20 users | 42 GB | 48 GB | ₹14,000/month |
Burstable RAM configurations advertise a "guaranteed" lower amount with bursting up to a higher figure. For Tally under concurrent load during GST filing — when all users are in the system simultaneously — the server needs the full RAM allocation consistently, not as a burst. Burstable configurations degrade precisely during peak load. Always confirm RAM is dedicated for Tally hosting.
Storage — NVMe SSD Is the Only Viable Option
Tally's database performs thousands of small random read/write operations per user session. IOPS (Input/Output Operations Per Second) for random small-block operations is the relevant storage metric.
| Storage Type | Random 4K IOPS | Tally Performance at 5+ Users | Verdict |
|---|---|---|---|
| NVMe SSD (PCIe 4.0) | 400,000 – 700,000 | Excellent — no degradation under load | Required |
| NVMe SSD (PCIe 3.0) | 200,000 – 400,000 | Very good | Acceptable |
| SATA SSD (enterprise) | 70,000 – 100,000 | Visible degradation with 3+ users | Inadequate |
| SATA SSD (consumer) | 40,000 – 70,000 | Significant degradation with 2+ users | Unacceptable |
| HDD (7200 RPM) | 100 – 200 | Unusably slow | Never appropriate |
Storage capacity guidance: A typical Indian SME's Tally company database (3–5 years, moderate transaction volume) occupies 2–10 GB. A CA firm with 50 client companies at 500 MB to 2 GB each requires 25–100 GB for Tally data. Adding OS, Tally installation, TDLs, and Windows files, total server storage of 80–200 GB covers most deployments. M A Global Network provisions NVMe storage sized appropriately for your workload.
CPU — Dedicated vCores, Not Shared
Tally is not a heavily CPU-bound application under normal accounting usage. CPU becomes relevant during intensive operations: GSTR-2A/2B reconciliation on large transaction volumes, year-end closing processes, and bulk data entry periods.
The recommended CPU allocation follows a simple rule: 1 vCore per 2 to 3 concurrent users, plus 2 baseline vCores for the OS and background services. For a 10-user server: 2 (baseline) + 4 (10 users ÷ 2.5) = 6 vCores minimum, 8 vCores recommended.
Shared or "burstable" CPU creates the same problem as burstable RAM — contention during peak load exactly when reliable performance is most needed. M A Global Network provisions dedicated vCores on all plans.
Firewall Configuration Best Practices
The correct firewall configuration for a Tally cloud server prioritises minimising attack surface while maintaining access for all authorised users.
- Allow RDP (TCP 3389) from authorised IP addresses only — whitelist office IPs, staff home IPs, and any branch office IPs. All others: drop.
- Block all other inbound connections — the server should only receive traffic from known sources
- Allow outbound HTTPS (443) from server — required for Tally GST e-invoice API calls, Windows Update, backup upload to off-site storage
- Log all inbound connection attempts — for security audit and incident investigation
Backup Configuration — What Good Looks Like
An adequate backup configuration for Tally cloud hosting:
- Daily full backup of all Tally company data directories — captured after business hours
- Off-site storage on separate infrastructure — physically and network-separate from the primary server
- Minimum 7-day retention — enables restoration from any point in the past month
- Monitored completion with alerting — backup failures generate immediate alerts
- Periodic restoration testing — a backup that has never been tested may not restore correctly
M A Global Network implements all five elements as standard. Backup jobs are automated, completion is monitored, and retention is 7 days minimum on all plans.
Complete Configuration Summary
| Specification | M A Global Network Standard | Why It Matters |
|---|---|---|
| Operating System | Windows Server 2022 | Only OS supporting multi-user concurrent RDP |
| RDS Licensing | CALs included per user | Legal compliance for concurrent RDP sessions |
| RAM | Dedicated, sized above minimum | Prevents paging under concurrent load |
| Storage | NVMe SSD (PCIe 3.0 minimum) | 300,000+ IOPS for concurrent database operations |
| CPU | Dedicated vCores, not shared | Consistent performance during peak operations |
| Firewall | IP-whitelisted at network level | Eliminates automated attack surface |
| Backup | Daily off-site, 7-day retention, monitored | Recoverable from any event within past month |
| OS Patching | Managed, scheduled | Removes known vulnerability exposure |
Frequently Asked Questions
Yes. M A Global Network provides full specification details — OS version, RAM allocation, CPU cores, storage type and size — in writing before you confirm a plan. These specifications are confirmed, not approximated. The ₹700/user/month rate reflects the specifications for the correctly provisioned configuration for your concurrent user count. There are no "performance tier" upgrades required to get the specifications described in this guide.
The server is resized — more RAM and CPU cores allocated to the existing instance. This is a managed operation handled by M A Global Network, typically completed within a few hours with a brief maintenance window. Your Tally data, TDLs, user accounts, and configurations are completely unchanged — only the underlying server resources increase. You are charged at the ₹700/user/month rate for the new user count from the date of the upgrade.
Yes, even for small setups. NVMe vs SATA SSD affects Tally startup speed, company file opening time, and report generation speed for all user counts — not just multi-user scenarios. A sole-proprietor Tally user on NVMe experiences noticeably faster application performance than on SATA SSD. For 3+ concurrent users, the difference becomes very significant because concurrent database I/O is where NVMe's IOPS advantage compounds.
Correctly Specified Tally Cloud — No Guesswork
Every plan configured to the right spec for your user count from day one. ₹700/user/month, all-inclusive.