Computer audit parameters

[BeeJayEff]

We have an A2013 database split into FE and BE, with up to ten client PCs running local FEs. The performance of two clients is an order of magnitude better than the others (regardless of what functions they or others are running), but this does not seem to correlate with their processors or amount of RAM. As a trial, I tried each client running the FE on the server itself; they all achieved similar performance to the two "good" clients running local FEs.
Given the size of the discrepancy, I do not currently think that it can be an Access issue, but as the boss has nominally the best machine yet suffers the worst performance , I need to address the issue to stop him bad-mouthing Access.
Before embarking on a complete audit of all the clients, what parameters should I gather for each :
Processor (number of cores, clock speed), RAM, network configuration (what parameters exactly ?), swap file config, disk free space/fragmentation, ...

Anything else ???

 

[smig]

You opened a post for the same issue before
Performance Issues

 

[BeeJayEff]

You opened a post for the same issue before

Same issue, but I want to focus specifically on differences between the clients, rather than general Access performance tips.

 

[gemma-the-husky]

make sure there is a persistent connection to the back end.

make sure there is plenty of ram. later versions of access need increasingly more.

make sure your boss does not have hundreds of things running. virus checkers can slow things down.

is he on the same LAN as every one else?