UGREEN NAS Slow with Multiple Users? Find the Bottleneck

If your UGREEN NAS performs well for one user but slows down when several people connect, a shared resource has reached its limit. The constraint could be network bandwidth, storage latency, CPU usage, memory pressure, or a background service competing with active users.

TL;DR

First Confirm the NAS Is Fast for One User

If one computer is already slow, adding more users only makes an existing problem more visible.

Connect one computer to the same router or switch as the NAS using Ethernet. Copy a unique 10GB or larger file between the computer and a shared folder, then record the sustained transfer speed.

If the single-client result is already below the expected speed for the negotiated network connection, follow our slow UGREEN NAS transfer diagnostic first. That guide covers incorrect link negotiation, Wi-Fi, cables, small files, SMB behavior, and transfers that start quickly before slowing down.

For a more controlled network and storage benchmark, use the procedures in our UGREEN NAS speed-test guide.

Continue with the multi-user test only after one wired client performs normally.

When the Network Is the Shared Limit

The network is the likely bottleneck when aggregate throughput remains near the practical ceiling while CPU and storage activity stay below their limits.

For example, five active users cannot each receive 125 MB/s through one 1GbE connection. Their combined traffic still has approximately 125 MB/s available. Moving to 2.5GbE raises that shared budget to approximately 312.5 MB/s when the NAS, switch, client adapters, and cabling all support the faster connection.

Before upgrading, confirm that every part of the path supports the intended speed:

• The NAS network port
• The client network adapter
• The router or switch
• The Ethernet cable
• The negotiated link speed
• Any dock or adapter between the client and network

A 10GbE NAS connected through a 1GbE switch still operates at 1GbE.

Use Link Aggregation for several simultaneous connections

A UGREEN NAS with multiple network ports can combine them through Link Aggregation. This is especially useful when several clients access the NAS simultaneously.

UGOS Pro supports several Link Aggregation modes:

• Bond6 Adaptive Load Balancing: Does not require Link Aggregation support on the switch.
• Bond4 Dynamic Link Aggregation: Uses LACP and requires a compatible, correctly configured switch.

Link Aggregation can distribute suitable connections across multiple physical interfaces, increasing aggregate throughput and providing redundancy. One ordinary connection generally remains limited to the speed of one physical link.

Where both endpoints support and are configured for SMB Multichannel, one workstation may establish several SMB connections across multiple network interfaces. This is different from expecting one normal TCP session to use the combined speed of a bond.

To create a bond in UGOS Pro, open Control Panel > Network > Network Connection, select Link Aggregation, and choose the mode that matches your network.

Creating or removing a bond briefly interrupts network access. Review any firewall and traffic-control rules tied to the original interfaces after the change and recreate them where necessary.

For broader network and Link Aggregation troubleshooting, use our UGREEN NAS performance bottleneck guide.

Prevent one service from consuming all outbound bandwidth

Sometimes the network is full because one service—not another user—is consuming most of it. A cloud upload, download task, container, or backup job can compete with people opening shared files.

UGOS Pro Data Control can apply minimum or maximum outbound bandwidth to a built-in service or selected port:

1. Open Control Panel > Network > Data Control.
2. Select Add.
3. Choose the relevant network connection.
4. Select a built-in service such as SMB or NFS, or enter the custom port used by the application.
5. Set the appropriate minimum or maximum bandwidth.
6. Review the rule order when several rules apply.

A maximum limit can stop a background service from taking the NAS’s entire outbound connection. Minimum bandwidth and rule priority can give an important service greater access when several services compete.

Data Control works by service or port. It does not guarantee equal bandwidth to individual users sharing the same SMB service, and outbound limits do not control files being uploaded from a client into the NAS.

When the Storage Pool Is the Shared Limit

If network usage remains below its ceiling while storage activity rises sharply, the drives or storage pool are struggling to serve the combined workload.

Large sequential transfers are relatively easy for an HDD array. Several users opening different small files force the drive heads to move repeatedly between file locations, increasing latency and reducing total throughput. This is why an array can perform well during one large file copy and feel slow when several users browse project folders at the same time.

The appropriate change depends on the workload:

• Keep large archives, media libraries, and sequential backups on the HDD pool.
• Place virtual machines, databases, container data, and heavily shared small files on a compatible SSD storage pool.
• Use SSD cache for frequently repeated access to hot data.
• Do not expect read cache to transform one-time transfers of large files that have not been cached.

M.2 SSD roles vary by NAS model and storage configuration. Our guide to using HDDs and SSDs together in a UGREEN NAS explains when to use an SSD pool and when cache is more appropriate.

Also check whether the NAS is rebuilding RAID, running Data Organizing, scanning for malware, generating media thumbnails, indexing photos, or processing backups. These jobs can produce sustained drive activity even when no user is copying files.

If RAID synchronization or a rebuild is active, follow the dedicated slow NAS RAID synchronization guide before changing hardware.

When CPU or Memory Is the Shared Limit

High CPU usage with moderate network and storage activity usually points to processing performed by a protocol, application, or container.

Common examples include:

• Media transcoding
• Photo recognition and indexing
• Antivirus scanning
• Docker containers
• Virtual machines
• Encrypted or signed SMB traffic
• Database activity
• File compression or extraction

Use Task Manager to identify the service or process consuming the CPU. Pause that service briefly and repeat the concurrent transfer test. If performance returns immediately, you have found the conflict.

UGREEN NAS processors are not user-upgradable. If a required application consistently saturates the processor, the practical options are to reduce its workload, move it to another system, run it at a different time, or choose hardware with more processing headroom.

{{UGPRODUCT}}

Additional RAM helps when Task Manager shows sustained memory pressure from applications, containers, virtual machines, indexing, or many active services. It does not increase the throughput of a saturated 1GbE connection.

Supported memory capacity and module requirements vary by model. If testing proves that the processor, memory ceiling, network ports, or storage configuration cannot support the required workload, you can browse and filter UGREEN NAS storage by bay count, processor, memory, and network connectivity.

Schedule Workloads That Do Not Need to Compete

Where possible, schedule these jobs outside busy hours:

• Computer and server backups
• Cloud synchronization
• Photo and media indexing
• Antivirus scans
• RAID maintenance and Data Organizing
• Large downloads
• Thumbnail or preview generation

Do not permanently disable backup, security, or storage-maintenance tasks to make the NAS appear faster. Move them to a quieter period, then confirm that they complete before the next active window.