When we saw response times of around 20 milliseconds for a full round-trip function execution, our concerns were eased!
How many ms is that for starting the tab rather than execution? I wonder if this could be further reduced if we could pre warm X number of tabs in memory.
The current version actually keeps a pool of blank tabs open. This improved Firefox performance quite a lot, but didn't have a major impact on Chrome (although Chrome still outperforms Firefox a lot). The main delay seems to be from the IO of loading the function web page. I'm sure it can be optimized further with browser caching.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How many ms is that for starting the tab rather than execution? I wonder if this could be further reduced if we could pre warm X number of tabs in memory.
The current version actually keeps a pool of blank tabs open. This improved Firefox performance quite a lot, but didn't have a major impact on Chrome (although Chrome still outperforms Firefox a lot). The main delay seems to be from the IO of loading the function web page. I'm sure it can be optimized further with browser caching.