Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • Not sure if that's the case, JavaScript wouldn't care if you were just deployed, server side code is what feels sluggish afterwards... Commented Apr 29, 2013 at 16:54
  • You have to think about that ask data to client.svc that is hosted on IIS Commented Apr 29, 2013 at 16:58
  • Good point now that you mention it, so my curiousity is how fast does this happen after reload? Commented Apr 29, 2013 at 17:07
  • because IIS has all the data in memory. Commented Apr 29, 2013 at 17:17
  • Sorry, I should have made this clearer, but this is well after a deploy. I know you can't see it (and I wasn't aware of this before I posted that you couldn't get the original size of the image) but the call to /_api/contextinfo in that run was 46ms, the shortest I've ever seen it. That was like the 10th run in a row. Regardless of when I run the test, there's usually ~1s gap between the last Web Resource and my POSTs. Commented Apr 29, 2013 at 17:32