You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 3, 2019. It is now read-only.
This was on the hive-us.heruko service, still extremely slow. It's like it's intentionally being forced to wait a few second before loading to the next screen. Why does it take so long in the first place?
It's takes from 30 seconds to one minute to login and sync, and even longer to create a new wallet. These times should be under 10 seconds, preferably 5 seconds.
The reason for all this is because people are lazy, and these days decide not to use apps which seem to load for long periods of time, and just stop using the app.
The text was updated successfully, but these errors were encountered:
Can't Hive-JS be deployed on an AWS instance? Or even something like
DigitalOcean.
How much RAM, SSD space and compute power do you need? These can be easily
afforded. If it is a small instance, I'll pay for it.
I'm going to try to run this on a local instance and run diagnostics to see
why this is running slowly. If it's just Heroku being slow, I could help
contribute to running costs, maybe a crowdfunding service could help.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This was on the hive-us.heruko service, still extremely slow. It's like it's intentionally being forced to wait a few second before loading to the next screen. Why does it take so long in the first place?
It's takes from 30 seconds to one minute to login and sync, and even longer to create a new wallet. These times should be under 10 seconds, preferably 5 seconds.
The reason for all this is because people are lazy, and these days decide not to use apps which seem to load for long periods of time, and just stop using the app.
The text was updated successfully, but these errors were encountered: