pettit87 Posted November 22, 2012 Posted November 22, 2012 Since the new release of SIMS our SIMS server has been running at 100% RAM & CPU. Has anyone else experienced this problem? The server has been restarted. Is it possible to downgrade?
synaesthesia Posted November 22, 2012 Posted November 22, 2012 SIMS has always eaten RAM like a starving wolf let free in a field of sheep, but CPU, that's worrying. Is it pulsar.exe that's consuming both? or SQL?
pettit87 Posted November 22, 2012 Author Posted November 22, 2012 It's the SQL Service. Its causing a lot of problems with users using SIMS and is effecting PARS - This reads the SIMS database for attendance and is becoming a bit concern
glennda Posted November 22, 2012 Posted November 22, 2012 On the sims client has it enabled the graphs on the home screen? These have always caused problems with Sims.
pettit87 Posted November 22, 2012 Author Posted November 22, 2012 Glennda - Please can you advice on how to do this
Max_Power Posted November 23, 2012 Posted November 23, 2012 Since the new release of SIMS our SIMS server has been running at 100% RAM & CPU. Has anyone else experienced this problem? The server has been restarted. Is it possible to downgrade? Not done the update yet as it gets released via solus 3 today - have you managed to find out off capita if its happening elsewhere?
PhilNeal Posted November 23, 2012 Posted November 23, 2012 It's early days as yet but no issues raised so far. I'd like to think we'd have spotted this type of thrashing in our test environments and early adopter schools. The suggestion of looking at the refresh rates on the home page widgets is sound but the defaults shouldn't cause these issues.
vikpaw Posted November 24, 2012 Posted November 24, 2012 I'm assuming it was fine before the update, so it's not the homepage widgets, unless you only just decided to turn them on. It's worth checking though, just in case someone decided to push them out to all staff. You can't really downgrade, you'd need to go back to an old backup, which means data loss. Try, Run validate memberships and dbdiagnostics as a precaution, just in case changes in the core have introduced validation errors or inconsistencies. Run the re-index patch. If you can, pause PARS and see how SIMS runs on it's own, without the extra read / write calls. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now