Closed breunigs closed 11 years ago
I’m down to < 300ms
locally. Will have to test this on production once upgrading to the new version.
Connection Times (ms)
min mean[+/-sd] median max
concurrency=1: 199 277 47.8 281 452 (home)
concurrency=2: 223 302 57.0 294 566 (home)
concurrency=2: 184 258 34.0 241 336 (uni internal)
The round trip times aren’t that great, being around 300ms. #83 (82b0a63) has increased the pressure to be fast and we miss the “appears instant” goal by about 200ms. Not yet sure why a more powerful machine takes longer to process the requests. The good news is that increased concurrecy does not really hurt the results.
latest patches brought down the time from 122ms to 107ms locally (when caches are primed that is, i.e. no admin/reviewer change has been made in the mean time)
Connection Times (ms)
min mean[+/-sd] median max
concurrency=1: 184 246 56.9 240 463 (home)
concurrency=2: 187 252 35.7 265 340 (home)
concurrency=2: 108 180 25.9 185 228 (uni internal)
i.e. down by about ~50ms compared to the last iteration. The official version has been updated.
I believe this has been improved to a reasonable low amount. I have about ~200ms at home and much of those 200ms are outside of my control. Please create new tickets if you find any pages that are particularily slow.
simply clicking "los geht's" on KeKs-production currently takes 10s to load the questions for my account. This is unacceptable.
I’m not sure why it takes that long. Even without the patches in f56c8d28757d303c609c, execution time was max. 1s locally. The server shouldn’t take 10 times that.