2 ms·
I probably shouldn't post this. Because: 1) I posted already a week or so ago. 2) Nothing much has changed, except, instead of running the demo on 1 giant mac
by graderjs 5y ago
I probably shouldn't post this. Because:
1) I posted already a week or so ago.
2) Nothing much has changed, except, instead of running the demo on 1 giant machine, I have 3 "always free tier" cloud machines (AWS t2.micro in N Virginia, Azure B1S in Iowa, and Linode Nanode in Singapore) and the GitHub pages landing page linked above runs a fetch against each and observed the duration with Resource Timing API
3) This will not be able to handle ANY load. Each tiny machine (1 vCPU, 1GB RAM) can barely handle running headless chrome suped up into a remote browser as it is, there is no way it will be able to handle multiple simultaneous.
So, I'm counting on the prior post and the opaque title to let this thing fly under the radar, so not many people will actually visit it.
If you see this and discover any bugs, security issues or what-not, and you mail me at cris@dosycorp.com I'll really love to hear from you. :)