Home Dashboard Directory Help
Search

SSAS Long server level lock during process update commit by ACALVETT


Status: 

Active


5
0
Sign in
to vote
Type: Bug
ID: 780659
Opened: 3/5/2013 3:13:51 AM
Access Restriction: Public
0
Workaround(s)
view
2
User(s) can reproduce this bug

Description

When a process update enters the second part of commit phase a server level lock is taken. On our system with around ~125,000 metadata objects and attached to a SAN the operation takes 3 minutes 22 seconds. Further detailed information on our process update can be found at http://blog.calvett.co.uk/2013/02/21/the-anatomy-of-a-process-update-part-2/

Our tests show that the commit is single threaded and that each delete is taking ~2ms and the only way we can improve the situation is to use SSD's to move delete performance into the nanosecond range but this is not viable.

We need to reduce the duration of the server lock so that our users do not experience what they consider to be a server outage.
Details
Sign in to post a comment.
Posted by Cos2008 on 3/5/2013 at 8:14 PM
had the same problem, on a large multidimensional project, at one of my clients and MS' recommendations, unfortunately, were reduce the number of objects or use SSD's as it "won't be fixed in the 2008R2 release" -- back then.
Sign in to post a workaround.