Hi David,

Please see my answer in lines.

Cheers,
Ionut C

From: Reyna, David [mailto:[email protected]]
Sent: Wednesday, May 14, 2014 6:52 AM
To: Chisanovici, IonutX
Cc: '[email protected]'
Subject: RE: Toaster performance testing - feedback

Hi Ionut,

The tools you reference look like they would be very valuable! Here are my 
initial notes:

  * A pragmatic question, do we plan to keep these tools internal, or do we 
want to release them at some point to our customers? I ask because the two 
tools look very useful and powerful, but they have licenses that may prevent us 
from re-distributing them. I presume that they are ok to look at since they do 
not appear to be GPL.

>IC: You guys have to answer to this question. In my opinion we should keep 
>this internal for the time being until we conclude that the toaster (globally 
>speaking) is performing as we want/expect. Also, I do not want to import the 
>two tools in the project as they are, I want to build this tool/script. I have 
>provided those links only as references for what I intend to do.
>IC: In the original mail I had a question: how, you guys, suggest to integrate 
>this tool ? as a toaster internal application or as a standalone script ?

  * We should probably iterate what exactly are our goals, and how we plan to 
act on that data. Here is my quick list.

    (a) Validate URLs, report broken links to developers
   (b) Measure page response times, provide developers regression plots and 
potential performance problem areas
    (c) Measure SQL queries per page, report excessive/broken requests to the 
developers
    (d) Maintain Toaster databases for off-line regression tests, run these 
tests on a periodic basis and report errors to
    (e) Provide easy runtime usage, have developers run these tools as part of 
their bug submission pretests
    (f) ?

>IC: agree on all points, please give more explanations for the d point.

  * Is there also a requirement about Toaster Validation tools?

    (a) Your tool will do URL validation. That is very good to have.
    (b) It would also be good to have a tool to check every HTML link to see 
that those are also all valid.
    (c) We could have some "gold-standard" pages that we can compare against 
looking for data regressions.

>IC: agree on all points. For the b point, my intention is to have the 
>possibility to check either all urls/sql ... at once, either only one page/url 
>and its own backend sqls

- David


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Chisanovici, IonutX
Sent: Monday, May 12, 2014 12:12 AM
To: '[email protected]'
Subject: Re: [Toaster] Toaster performance testing - feedback

Hi guys,

Kind reminder.

Thanks,
Ionut C

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Chisanovici, IonutX
Sent: Thursday, May 08, 2014 11:18 AM
To: '[email protected]'
Subject: [Toaster] Toaster performance testing - feedback

Hi guys,

Regarding toaster performance testing 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6009, as discussed yesterday 
in the meeting, I need your feedback on my following proposal.

I was thinking to develop this like a django profiler tool.
This will be a script (django snippet) or an toaster internal app (toaster 
performances can be seen from the browser) that will parse all deployed 
applications urls from each urls.py, will log all broken urls (everything 
except http code 200 and redirect codes) for debug, and after excluding those 
broken urls will log the response time for the good ones to see how fast/slow 
the pages will load.
Also, for the good urls (http code 200), the script will get all backend sql 
queries and log/show the response time for them.
For the sql queries we might encounter broken sql queries. (broken sql queries 
are the ones that return no results from various reasons). These queries must 
be also resolved.

As an example, you can see these two links:
http://www.morethanseven.net/2011/06/30/Django-performance-1-measuring-performance/
  (see the django timelog part)
https://djangosnippets.org/snippets/461/

Having the above, please feel free to comment, to give suggestions, to give 
improvements.

Thanks a lot,
Ionut C
-- 
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster

Reply via email to