[Qgis-psc] Performance regressions (was QGIS 2.18 bug fixing effort)

[Régis Haubourg]

Hi,
we just had a chat with 3Liz about a performance benchmark for qgis server.
If qgis.org has an infrastructure for hosting that, it would help a lot.

We also have a OGC compliancy tester in a docker producing html reports. We
miss some public location in QGIS.org to push those reports. Where could
that be?

Cheers
Régis

2017-05-24 14:56 GMT+02:00 ElPaso <elpaso at itopen.it>:

> Il 24/05/2017 14:29, Paolo Cavallini ha scritto:
>
>> Il 24/05/2017 14:25, Matthias Kuhn ha scritto:
>>
>>> I think this is still usable (qgis_bench IIRC).
>>>
>>> What it does: give usable measurements when executed on the same
>>> environment for different projects, different QGIS versions, different
>>> build parameters, different databases...
>>>
>>> What it not does: produce values that are comparable when executed on a
>>> non-stable system like travis CI. Performance on this system varies from
>>> day to day and we are never sure if a code change or some other change
>>> on the system (hardware, software, operating system...) is responsible
>>> for some measured "performance regression".
>>>
>> Thanks Matthias for reminding.
>> So it would be best to run it in an isolated, predictable environment.
>> Would a VM do? I think we could find the resources for it, even if this
>> would require having a dedicated server.
>> All the best.
>>
>
> Maybe a Vagrant configuration to be run on AWS (or any other Vagrant
> compatible provider).
>
> What we probably need is something we can spin up and switch off just for
> the time required for the test, that's why AWS would fit.
>
>
> Just my 2 cents.
>
> --
> Alessandro Pasotti
> w3: www.itopen.it
>
>
> _______________________________________________
> Qgis-psc mailing list
> Qgis-psc at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20170524/51a980c6/attachment.html>