[Cdash] Performance Issues

[Julien Jomier]

It takes about 2-3 seconds, but the database is only 4GB (we haven't 
done the full import). I think there is room for improvement here. I'm 
profiling the SQL requests.

Julien

Bill Lorensen wrote:
> So on the internal machine, how many elephants do you count to bring
> up an ITK Test/Summary page as reported in:
> http://public.kitware.com/Bug/view.php?id=6517
> 
> Bill
> 
> On Thu, Mar 6, 2008 at 11:59 AM, Julien Jomier
> <julien.jomier at kitware.com> wrote:
>> Bill,
>>
>> We are actually forwarding ITK and CMake dashboards to one of our
>> internal machine and I'm not seeing any major performance issues but I'd
>> like to have CDash on public run a little bit better.
>>
>> Julien
>>
>>
>> Bill Lorensen wrote:
>>> Julien,
>>>
>>> Would it be possible to run cdash on another machine? Especially early
>>> in its development, it's hard to assess performance on a heavily
>>> loaded machine. I remember that early Dart2 performance problems were
>>> not Dart2 issues but rather other loads on the system we were using.
>>> Perception is sometimes more influential than reality.
>>>
>>> Bill
>>>
>>> On Thu, Mar 6, 2008 at 11:44 AM, Julien Jomier
>>> <julien.jomier at kitware.com> wrote:
>>>> Bill,
>>>>
>>>> Thanks a lot for the report. This is really helpful.
>>>> I'm working on these issues. There is a part of tuning, but also a part
>>>> of Dart1 rollup that is using a lot of CPU on public.kitware. This
>>>> latter should go away when we stop using Dart1. As you know, we are
>>>> running a lot of services off of public.
>>>>
>>>> I'm keeping an eye on these issues.
>>>>
>>>> Julien
>>>>
>>>>
>>>> Bill Lorensen wrote:
>>>>> As suggested earlier, I've started to add performance issues to the
>>>>> bug tracker. It might be helpful if each page showed the generation
>>>>> time at the bottom of the page (like on the main dashboard page).
>>>>> Right now I use the one elephant, two elephant technique.
>>>>>
>>>>> I find the overall feel of the ITK dashboard to be sluggish in
>>>>> general. A mid-day dashboard view of ITK usually takes over 5 seconds.
>>>>> The Cmake dashboard is very responsive, but CMake has a small number
>>>>> of tests compared to ITK.
>>>>>
>>>>> I am not a expert, but these performance issues probably have to do
>>>>> with database tuning, index selection, batching queries, etc. I
>>>>> remember back in the GE CRD Frost days, that Dan Blezek did a lot of
>>>>> tweaking early on. I think he also built some page mechanisms.
>>>>>
>>>>> I know CDash is still in beta, but I think performance improvement
>>>>> should be the top priority. Early impressions are important.
>>>>>
>>>>> Bill
>>>>> _______________________________________________
>>>>> Cdash mailing list
>>>>> Cdash at public.kitware.com
>>>>> http://public.kitware.com/cgi-bin/mailman/listinfo/cdash
>>>>>
>