Jump to content

Recommended Posts

Posted
18GB ram, 4 CPU cores shown to VM, SQL databases on SSD storage, Server 2008R2 and SQL 2008 for sims/fms and another SQL2008R2 instance with about 8 databases. My Server is also going crazy with cpu usage but only on the SQL2008 instance, so spec doesn't seem to make much difference.

 

The only thing that lets that setup down is the number of cores...

Posted
The only thing that lets that setup down is the number of cores...

 

Well you could say so but the spec started lower and grew as requirements did. It's only in very recent weeks that the CPU usage has ever been a problem and all that is coming from the sims database. CPU usage on all the other 10 databases on the server is tiny, and sims certainly never used to be this bad!

 

I could allocate all 8 cores to it but I certainly feel based on the evidence that i'd only be covering up the problem rather than fixing it, which I'm not a fan of.

Posted
Good job we shifted over to the new server then! Due for our update soon. Our old SQL server would've melted.

 

What OS are you using? We've just upgraded to Server 2012 and had to keep the old server running SQL2008 for the time being. Our LEA has told us not to do the update for the time being because of the issues.

Posted

Patch 18148 is now live.

 

According to a post on SupportNet, it sets the refresh for the timeline to 30 minutes. Apparently, it does not alter the ammount of data being collected though so the same CPU hit on the server per refresh remains the same, but it should be once every 30 minutes.

  • Thanks 1
Posted
Interested to hear what happened to those LAs who host multiple school DBs on one server. They must have just stopped first thing for AM reg..
Posted
Our LEA has advised us to reconfigure Teacher Timeline refresh rate to 900. I don't know if it works yet because we've not done the upgrade.

 

Ours is already at 900 (aka 15 minutes) but still very slow.

 

Peter

Posted

Another Supportnet update regarding the current "fix":

 

Whilst patch 18148 has improved performance it is not as efficient as we would wish. So that users can benefit from the new fuctionality additional work is taking place. The fix will be released as soon as possible. This news item will be updated as soon as we have an further information.

  • Thanks 1
Posted

...and a further update with an altered patch for lengthening the poll time even more for large schools and LAs. I figured they must have been crippled.

 

Home Page Performance issues further update

 

 

Following my original News Item dated 19/04 and its subsequent updates, I now have a further update.

 

We have identified a number of areas where we could improve the performance of the homepage

 

The first solution is via the application of patch 18148 which changes the refresh rate of the new timeline widget to 30mins and batches users so that they are not requesting data at the same time.

 

Further investigations have shown that we have needed to improve on the performance even further for larger schools and especially LAs that host SIMS for schools. We have now re-written parts of the homepage, which will be extensively tested before being released towards the end of next week. In the meantime there is an on-demand patch 18170 for hosted LAs that will change the refresh rate to two hours.

 

Please accept our apologies for the inconvenience caused by the time taken to improve the performance of the homepage and therefore the delay for some of you in using the enhanced functionality provided by the spring release.

[TABLE=width: 100%]

[TR]

[TD=align: left]Posted: 26th April 2013 by Geoff Perry[/TD]

[/TR]

[/TABLE]

  • Thanks 1
Posted
Another Supportnet update regarding the current "fix":

 

Whilst patch 18148 has improved performance it is not as efficient as we would wish. So that users can benefit from the new fuctionality additional work is taking place. The fix will be released as soon as possible. This news item will be updated as soon as we have an further information.

 

Hi

 

The update regarding the fix looks about right.

 

Put the patch on Thursday evening and monitored the SIM's Server yesterday and although this has improved the situation to some extent still extremely high CPU usage compared to before the Spring relaese, I have also spoke to a couple of users that were having issues before and they have said that it does seem to be performing slightly better but am not 100% confident that this has resolved the issue looking at the high CPU usage.

Posted
Ours is already at 900 (aka 15 minutes) but still very slow.

 

Peter

 

Thanks for doing the maths for me :) I think I read somewhere that the patch pushes it up to 30 minutes.

Posted

are you running solus 3 on the sims server

 

ive just been watching our server and the solus3 deployment services was eating cpu time somthing stupid. ive disabled it for now and its calmed down a bit sql is still hammering away so still not perfect but a bit better

Posted
are you running solus 3 on the sims server

 

ive just been watching our server and the solus3 deployment services was eating cpu time somthing stupid. ive disabled it for now and its calmed down a bit sql is still hammering away so still not perfect but a bit better

 

Yea, I've seen this too. SOLUS3 tends to suck up all free CPU/RAM when a deployment is initiated. Sometimes it slows the server down so much that the SOLUS3 UI reports the service is not responding when in fact it is still running!!!

Posted
The patch designed to give a complete fix is now available to support units. If they don't release it to you and you have been impacted then please request it from them.
  • Thanks 2
Posted
@PhilNeal we were impacted by the issue originally and raised this with the LEA who installed Patch 18148 and was still initially giving us issues but seemed to vastly improve after Server re-boot, but still having slight issues when running reports only in regards to speed these run at etc. Would you suggest deploying the Patch or waiting a little ?
Posted

@Stephen_cleaver the patch is a better fix as it doesn't rely on slowing down the polling. Slowing the polling means that you can't rely on the information on the home page being current.

 

I don't think it is likely to fix any reporting issues unless these were caused by overworking of the server.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...