Hi Andreas,

The select top 10 * from sys_l_stat order by waits desc; queries from the 8891 
& 8895 instances do not show an excessive number of waits, only about 1990+ 
waits on the SYS_DAV_QUEUE index. When you ran those queries was the system 
under  typical work load ie  was the long running query being run at the time ? 
Note you should also run the query a number of time to get a sample of the 
waits as indicated at:

        http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#perfdiaglocking

I certainly would have expected a larger number of waits on the 8891 instance 
where the "WARNING: * Monitor: Many lock waits”  errors where occurring 
extensively in the log …

You indicate the "transaction deadlock and No ext map for dp 3193852 in 
uncommitted blob cpt” on the 8895 instance only occur when running several 
queries in parallel, so this would be the time to be running the query to check 
for locks/waits. How many of these queries are typically being run in parallel 
? Also are these queries being executed via the /sparql end point ie HTTP  or 
SQL interface ?

Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc.      //              http://www.openlinksw.com/
Weblog   -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-software/
Twitter  -- http://twitter.com/OpenLink
Google+  -- http://plus.google.com/100570109519069333827/
Facebook -- http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers



> On 2 Mar 2016, at 17:31, Nolle, Andreas <no...@hs-albsig.de> wrote:
> 
> Dear Hugh,
> 
> please find the requested information about top50 
> athttps://www.dropbox.com/s/ylrb20ylze38cj6/top50.zip?dl=0
> 
> Please notice that both errors (transaction deadlock and No ext map for dp 
> 3193852 in uncommitted blob cpt) only occur if I run several queries (of the 
> type already mentioned) in parallel.
> Since my assumption is that especially the transaction deadlock error is 
> probably related to the long evaluation time, I haven’t restarted my 
> application so far…
> However, I will run a database integrity check and perform a +crash-dump and 
> restore to eliminate the “uncommitted blob” errors in the next run of my 
> application.
> 
> Best regards
> Andy

Attachment: smime.p7s
Description: S/MIME cryptographic signature

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Reply via email to