Changes between Initial Version and Version 1 of Ticket #11573, comment 7


Ignore:
Timestamp:
Sep 13, 2014, 8:40:21 PM (5 years ago)
Author:
iwakeh
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11573, comment 7

    initial v1  
    11* It might be also interesting to look at the access log in terms of how many request were there at a given instance in time.
    2 * Maybe, separate the lookup and prepare measurements from the response times. Response times could be longer if the connection of the client is slow, or not correctly terminated, or in case of too many concurrent session threads (that's why I asked about access logs). Seperate lab-measurements for lookup and compile could be easily compared to db solutions. Seperate response time measuremnts in-vitro and in-lab might help identifying server issues.
     2* Response times could be longer if the connection of the client is slow, or not correctly terminated, or in case of too many concurrent session threads (that's why I asked about access logs). Too many concurrent sessions would slow down lookup and compile in addition.
     3* Maybe, also separate the lookup and prepare measurements "physically" from the response times. Seperate lab-measurements for lookup and compile could be easily compared to db solutions. Seperate response time measuremnts in-vitro and in-lab might help identifying server issues.
    34
    45* Pondering the database question should not only be done b/c of performance reasons, but also in the light of what Onionoo serves. Many requests especially those using the history subtype are database concerns.Future requests (like #13137) too. Databases are made for that;