SPServices async performance

Question

SpServices does offer the most user friendly piece of code on SharePoint, but if we enable async it still lags behind in performance when compared with the client model, any reasons?

Or am I missing something in my implementation ?

Answer 1

SPServices uses the old SOAP service API, which although are deprecated, they continue to be a very fast API - especially for GetListItems...

In your follow up answer above, you show a snippet of code calling SPServices in synchronous mode (async: false) - meaning: your entire browser will "freeze" until the request is returned from the server and your callback is done doing its thing... This is not (in my mind) "enabling" async, but rather disabling it.

This is why I wanted to see 2 complete code samples... I doubt that CSOM is executed in synchronous mode... Actually: in client side development almost nothing should be done synchronous if you care about at all about UX.

My Advice is to NOT set the async parameter to SPServices or set it to true (the default)...

Answer 2

I found the answer the SOAP API async requests though drastic , The throughput of individual request were way better than CSOM Object call.

The profiling confirmed the same. Thanks @Paul T