-
Your thoughts are valid, but not always. There is an assumption in there that the load constraint is based on CPU, disk, or memory. If it is an inherrent design flaw, no amount of load sharing will fix the problem.
In my own case, CPU load on the server is negligible during testing with everything else turned off. Memory capacity is not a problem either. That leaves storage bottlenecks. I did actually find a problem there, which I have subsequently fixed, but there are still other architectural problems in the code base that dont get fixed with horizontal scaling.
As a side reference - the storage issue I found was poor write speed performance via a Raid controller. Replaced some drives, and now screaming fast storage.
-
You're right. What I mean is that building a social network assumes a massive and scalable number of users and content. For UNA to be viable, it must run quickly whether it's handling just a few users on a single cloud server or millions of users across one or multiple server clusters. The modularized applications need to be optimized to ensure performance at any scale.
The real problem, however, is loading time. As I mentioned, it doesn’t matter which server is tested even a single user experiences around five seconds of loading, which is far too long. With a five-second load time, the abandonment rate increases exponentially, starting after just one second. Nowadays, everyone is in a hurry. A site that takes five seconds to load is perceived either as non-functional or as low-quality and people are right.
As an investor, I wouldn’t put money into such a site. I expect to see this script fully functional before I commit. Investments in time, resources, and people are significant, and I have no reason to support a slow site in the age of speed. We’re no longer in the 1990s, when the internet was born and networks were slow. My perception is that UNA has potential, but there is a significant “but.”
It’s like I want to buy a tanker truck for my transport business, but the one being offered is full of holes. I would lose countless potential clients every second because it leaks or moves too slowly it’s exactly the same problem.
-
Yep. We're in agremeent. For my testing as I explained before, I've tested with zero other load on. (Firewall blocked all traffic except for my computer at home). Everything else was unchanged. Load was zero, Disk IO was zero. Network was zero. Even under those ideal conditions, it was performing like a dog. But let me give one more really concrete piece of information. I had migrated from Dolphin. Same data set, same hardware, same everyghing - but it just ground to a halt with Una.
Assuming the only thing that changed was Una, its pretty clear where the problem is. Dont get me wrong, it looks nice and has some nice features, but under the hood needs a little work.
-
I’m hoping the new NEO application, which was promised to also improve frontend speed, will be released soon. I have a Dolphin site that I’d like to migrate to UNA, but if performance stays this slow, it won’t make sense to move it. I’ll wait to test whether NEO brings real improvements, and then decide.
-
Comment to 'The need for speed'
Comment to The need for speed
