[Cdash] Database performance

Julien Jomier julien.jomier at kitware.com
Fri Jan 27 19:06:16 UTC 2012

Hi Tim,

I would recommend to enable asynchronous submissions in your 


This will let CDash receive the XML files and then process the 
submission asynchronously, without having time-outs (hopefully). The 
only minor drawback is that submissions are not instantly showing up on 
the dashboard.

Could you send us the queries that might be taking up some time and 
we'll try to investigate.


On 27/01/2012 04:08, Tim Gallagher wrote:
> Hi,
> We have the following setup for tests in our code:
>        ctest_configure(BUILD "${CTEST_REPO_DIRECTORY}" APPEND)
>        set(CTEST_BUILD_COMMAND "./setup.py -t ${TESTCASE} '{${LESLIE_BUILD_DICT_BASE}}'")
>        ctest_build(BUILD "${CTEST_REPO_DIRECTORY}" APPEND)
>        ctest_submit(PARTS Configure Build)
>      endforeach()
> Each build process generates something like 20K of data based on the output from CTest. After about 10 test cases, the submissions begin to time-out with:
>     Error when uploading file: /data/CTestScripts/leslie-release/leslie-TestData/Testing/20120127-0230/Build.xml
>     Error message was: Operation too slow. Less than 1 bytes/sec transfered the last 120 seconds
> When looking at the processes running on the server during this time, postgresql is busy running UPDATE and it takes progressively longer each time a submission comes in. There are over 200 tests, so only making it through 10 is a problem.
> Are there any suggestions on how to improve the performance here? Is this a problem with postgresql or with the SQL statements CDash uses? Has anybody come across this?
> Tim
> _______________________________________________
> Cdash mailing list
> Cdash at public.kitware.com
> http://public.kitware.com/cgi-bin/mailman/listinfo/cdash

More information about the CDash mailing list