Hello,
silly question. I'd just like some advice.
We currently have a Samba 4 file hosting server and a Samba 4 Active Directory server.
It works quite well except for Wednesday mornings when we have all 470 PCs connected.
The server's CPU is maxed out at 100%.
Explanation:
We use roaming profiles, and to reduce login time, we've stored the Mozilla Firefox and Google Chrome profiles on a network drive (appdata redirection).
So, when a user opens Google Chrome or Firefox, the profile is directly accessed from the network drive and opens files on the server.
After some tests with smbstatus, during these peak times, the server reaches 14,500 open files, of which 10,950 are for the Google Chrome and Firefox profiles.
I'm having trouble interpreting this number. Do you think the problem actually stems from the number of open files?
Or is it due to incorrect configuration?
Thank you for your feedback,
Simon
Number of files opened
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
That's a lot of open files.
The best solution is to disable browser cache to limit the number of files.
The best solution is to disable browser cache to limit the number of files.
Steven Samson - Tranquil IT Systems
Feel free to leave us your opinion on Wapt in the forum, or to answer our questionnaires
.
Feel free to leave us your opinion on Wapt in the forum, or to answer our questionnaires
.-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Actually, the cache is already redirected to local appdata.
Therefore, it's not synchronized upon logout.
The 10950 files are just history, bookmarks, extensions, etc.
I know Google advises against storing Google Chrome profiles on a network drive, but Chrome profiles are far too large to be stored in appdata. Login times would be too long.
Another observation I've made is that when a user logs in (downloading roaming profiles (approximately 5MB)) to htop, the user (PID) sometimes reaches 35% CPU usage on the server while downloading the profile, then stabilizes.
This seems excessive to me.
What do you think?
Simon
Therefore, it's not synchronized upon logout.
The 10950 files are just history, bookmarks, extensions, etc.
I know Google advises against storing Google Chrome profiles on a network drive, but Chrome profiles are far too large to be stored in appdata. Login times would be too long.
Another observation I've made is that when a user logs in (downloading roaming profiles (approximately 5MB)) to htop, the user (PID) sometimes reaches 35% CPU usage on the server while downloading the profile, then stabilizes.
This seems excessive to me.
What do you think?
Simon
