El 28/09/17 a les 10:29, Jérémy Mousset ha escrit:
Hi,
I like the idea of having tests on performances.
Testing performance is always a good idea. The problem is introducing it
on unit test as it can fail for some cases but you will want to accept
the change. Also we should update the test case for each improvement.
I'm not sure if checking the max number of queries for a given operation
is the best way to do it though. (as in some cases several small queries
can be faster than a single large one). It may be better than nothing
though.
The problem is what to measure, as probably the performance will depend
on the hardware, os and other unknown variables. For me the way to go
will be probably something like python speed [1] but this seems a lot of
effort.
[1] https://speed.python.org/changes/
--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk
--
You received this message because you are subscribed to the Google Groups
"tryton-dev" group.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tryton-dev/315e432c-86aa-0b92-52b5-f13b082c0056%40koolpi.com.
