This is somewhat off-topic, but has anyone here used SessionStack? How well does the service work, and is there a noticeable performance impact for the software to record on mid-range mobile devices? It looks really interesting and would probably be really helpful, but I can't include anything else in our applications that will further tax our already struggling lower-end devices with more code that needs to run and…
How JavaScript works: the rendering engine and tips to optimize its performance
11–14 of 14 posts
Re: How JavaScript works: the rendering engine and tips to optimize its performance
#12This is somewhat off-topic, but has anyone here used SessionStack? How well does the service work, and is there a noticeable performance impact for the software to record on mid-range mobile devices? It looks really interesting and would probably be really helpful, but I can't include anything else in our applications that will further tax our already struggling lower-end devices with more code that needs to run and…
We've been using SessionStack in our team for around 6 months now (along with their native Sentry plugin) and there hasn't been any impact on our web app (it's a quite heavy React app).
If you have any feedback or need assistance, you can always reach me at alex@sessionstack.com or ping us in our live chat inside the product :)
Re: How JavaScript works: the rendering engine and tips to optimize its performance
#13This is somewhat off-topic, but has anyone here used SessionStack? How well does the service work, and is there a noticeable performance impact for the software to record on mid-range mobile devices? It looks really interesting and would probably be really helpful, but I can't include anything else in our applications that will further tax our already struggling lower-end devices with more code that needs to run and…
I'm not sure about the implementation in Session Stack, but I work at LogRocket ( https://logrocket.com ) where we're solving a similar problem. We use a few methods to ensure that we have a minimal overhead on performance. - We use worker threads for data encoding and network I/O - We use the MutationObserver API for capturing diffs of the DOM - We pull static resources directly from an application's servers (vs upl…
I've poked around in the console a fair amount but would be really interested in two things you listed above:
- "We use the MutationObserver API for capturing diffs of the DOM"
- "We use Protobufs as a wire format for reducing bandwidth"
I know you all write pretty awesome JS articles on a regular basis but I have so many questions about how LR works! Spill the beans but not the secret sauce!
Re: How JavaScript works: the rendering engine and tips to optimize its performance
#14This is somewhat off-topic, but has anyone here used SessionStack? How well does the service work, and is there a noticeable performance impact for the software to record on mid-range mobile devices? It looks really interesting and would probably be really helpful, but I can't include anything else in our applications that will further tax our already struggling lower-end devices with more code that needs to run and…
I'm not sure about the implementation in Session Stack, but I work at LogRocket ( https://logrocket.com ) where we're solving a similar problem. We use a few methods to ensure that we have a minimal overhead on performance. - We use worker threads for data encoding and network I/O - We use the MutationObserver API for capturing diffs of the DOM - We pull static resources directly from an application's servers (vs upl…
Is this open sourced? I would like to understand how this works? (how do you capture network i/o?)