Scott Ribe wrote in post #1162964: > On Nov 20, 2014, at 12:42 PM, David Williams <[email protected]> > wrote: >> >> Essentially the fasted method for transferring data between >> client/server. > > That's literally a meaningless question. You're really going to have to > clarify your question before you can expect any answer. > > - Latency of individual requests and total number of requests throughput > are two different issues. > > - Getting data out of a database, getting static assets from cache or > disk, building responses to requests (whether HTML or JSON or whatever, > sending the responses to the browser, and rendering the result in the > browser, are all separate issues. > > So: lots of clients? busy clients? large requests? large database > backing the site? large or complex assets? complex processing of > requests? complex browser rendering?
You're right, it depends on the size of the service and how much data is actually being sent during each request. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/0ccb87d93f80876a4a16f9809fbf910c%40ruby-forum.com. For more options, visit https://groups.google.com/d/optout.
