|
|
 Rank: Umbracoholic
Joined: 9/8/2006 Posts: 1,410 Location: KY, USA
|
Slightly off topic... Certainly there are recursive calls to the database with GetMedia(), and that's an issue in an of itself. It should make a single call if possible. GetMedia() can make things slow in a hurry. Here's some background on that issue. http://forum.umbraco.org/yaf_postst2974_XSLT-libraryGetMedia-extremly-slow.aspxcheers, doug.
MVP 2007-2009 - Official Umbraco Trainer for North America - Percipient Studios
|
|
Rank: Aficionado
Joined: 7/23/2006 Posts: 171
|
Thanks for that pointer Doug - I didn't know that and this did something to the performance issue. But the restarting stille takes places.
I started on development on a new site and kept an eye on this problem because it don't happen on a clean install of Umbraco. I found out that when I installed my contact forms whit a lot of Ajax implementet - This couses the problem for me. I used an older version of the Ajax Control Toolkit - I updated my source with the latest release and this seems to fix the problem.
So a possible solution / cause to the bug could be updating the Ajax control toolkit.
thats all / Søren
Søren Linaa Level 1 & 2 Certified Professional
|
|
 Rank: Devotee
Joined: 1/10/2008 Posts: 61 Location: London
|
well, are we sure it's off topic ? I'm not talking about GetMedia itself, but about the ExecuteXmlReader function in the SqlServerHelper class which is used quite heavily throughout the code. My test with the "using" statement did made the job with keeping the connections to the DB to a decent standard, but opened new issues (publishing got wrong). I downloaded the very last changeset (32260), apply my 2 changes and every seems to work now. ExecuteXmlReader doesn't create multi DB connections and content is published as expected in a webfarm environnement. Maybe Ruben you can help us on this; I read on Codeplex there are been some issues with ExecuteXmlReader recently, any downside to have a "using" statement there ? cheers, seb http://www.be-k.net
|
|
Rank: Newbie
Joined: 11/15/2007 Posts: 2
|
Is there any news of a solution for this problem?
We have currently 2 websites running Umbraco on our dedicated win2003 with SQL Express 2005 and having the exact same problem. We can't see anything obvious in the event logs, there's no errors in the sql logs and our processor and memory usage are low across the board, BUT intermittantly both websites grind to almost a standstill!
They become almost totally un-responsive for a period of time before running as normal again. Until we can find out what the issue is we can't risk using this Umbraco for another client.
|
|
Rank: Newbie
Joined: 2/21/2008 Posts: 2
|
cpalm wrote:It could be a connection pooling problem (website is using to many connections). Adding this to you connectionstring might help Min Pool Size=5;Max Pool Size=500;Connect Timeout=10;
Performance monitors are great to find memory leaks or database pooling problems. On the webserver you should add a counter for Process -> virtual bytes -> select app pool Process -> private bytes -> select app pool
On the databaseserver you should add a counter for SQL Server General Statistics Object -> User Connections I've been having occassional performance problems and adding that to the umbracoDbDSN connection string in the web config seems to make a big difference
|
|
 Rank: Fanatic
Joined: 11/24/2006 Posts: 321 Location: Stockholm, Sweden
|
waterman wrote:Is there any news of a solution for this problem?
We have currently 2 websites running Umbraco on our dedicated win2003 with SQL Express 2005 and having the exact same problem. We can't see anything obvious in the event logs, there's no errors in the sql logs and our processor and memory usage are low across the board, BUT intermittantly both websites grind to almost a standstill!
They become almost totally un-responsive for a period of time before running as normal again. Until we can find out what the issue is we can't risk using this Umbraco for another client. I'm also still experiencing problems. It's taking up a lot of valuable developing time and frankly I'm getting a bit desperate. The thing that's most frustrating is that I don't know if the error is in: a) Umbraco b) IIS c) SQL Server ...or if it's a certaing combination/configuration that makes Umbraco unresponsive for a long time? I'm now going to try cpalm's addition to the connection string to see if it makes a difference. /THomas
Web Developer at Kärnhuset - http://www.karnhuset.net - Stockholm, Sweden
|
|
 Rank: Fanatic
Joined: 7/19/2006 Posts: 441 Location: Göteborg, Sweden
|
Thomas, what version are you using? I had these errors in a beta (the one with the datalayer) this winter. As soon as we upgraded to 3.05 they all disappeared. Or rather: the update let an SQL login error surface and made it possible to target the real problem - auto close where enabled in the DB... Anyhow, if you are using an unstable version built from source please switch to 3.05 that doesn't contain that experimental version of the datalayer... // ;) Kalle
" - Yeah I'd like to share your point of view, as long as it's my view too... ( http://www.d-a-d.dk/lyrics/pointofview)
|
|
Rank: Aficionado
Joined: 7/19/2006 Posts: 176 Location: Pittsburgh, Pennsylvania, USA
|
I can second Kalle's experience and suggestion. We have about a dozen umbraco sites running and we started experiencing the same symptoms along with deadlock errors showing up in server application log. Most sites were running v3.0.2....I upgraded all to 3.0.5 and all the issues went away.
Jason
|
|
|
Guest |