5 ms·
Could have been the browser? Or the network interface? Did you ever figure out why?
by alexk307 4y ago
Could have been the browser? Or the network interface? Did you ever figure out why?
- agloeregrets 4y agoDoesn't help that the pi 4 has a single-core performance that is 1/5th that of a current smartphone. If you are coming from fast hardware, the pi 4 is quite bad. I would love to see someone make a $99 product in this range with something moderately fast.
- PaulHoule 4y agoPeople have long been fascinated with "alternative" architectures for general purpose computing but most of the time you pay a little bit less (1/2) but pay dearly in terms of performance (more than 1/5 compared to a low end laptop.) It has a lot to do with why cable boxes suck. ARM is the first architecture in 20 years that competes with x86 on reasonably priced machines. (e.g. IBM POWER and IBM z are pretty quick but you can't afford them)
- Wowfunhappy 4y ago> ARM is the first architecture in 20 years that competes with x86 on reasonably priced machines. (e.g. IBM POWER and IBM z are pretty quick but you can't afford them) What about the PPC Macs? Yes, they were bad enough that Apple had to switch to x86—not exactly a ringing endorsement—but I'd say they were at least somewhat competitive, no?
- PaulHoule 4y agoYeah, the power macs were usable in the early 00's but they were slipping fast. I don't know if I'd count macs as "alternative" because, despite their good qualities, they are more locked down than PCs. SPARC was almost viable for a desktop machine in the early 00's, I had one under my desk that I was running a Sun Ray server on. We were hoping to use Sun Rays to provide access to the online catalog and other web resources but after Netscape became a non-viable web browser we were never able to get Mozilla to build on SPARC. It could have been ported but we didn't have the resources and nobody else bothered to do it. SPARC was slipping too and the price was not right.
- Wowfunhappy 4y ago> I don't know if I'd count macs as "alternative" because, despite their good qualities, they are more locked down than PCs. What do you mean here? Couldn't Power Macs run Linux?
- adamomada 4y agoI don’t remember much about it but they even had a bootloader called Open Firmware. Assuming its not a joke, GP has it dead wrong.
- johnklos 4y agoI don't know if I'd agree that SPARC would've ever been viable. The performance just wasn't there for the price. For instance, my 2002 AlphaServer DS25 with two 1 GHz CPUs runs many workloads noticeably faster than my 2007 Sun Fire V245 with two 1.5 GHz UltraSPARC IIIi CPUs. Also, Macs were never locked down. All Macs can run alternate OSes, from m68k Macs which can still run modern NetBSD without issues, to beige PCI Power Macs, to G3, G4 and G5 Power Macs, to Intel Macs, and now ARM Macs. Notably missing is support for NuBus Power Macs which requires more work than people are willing to do, although older MkLinux was available for them.
- jraph 4y agoPine64's RockPro 64 with 4GB RAM is $80 ($60 for the 2G version) and felt reasonably fast when one day I had to temporarily use it to surf the web. Mind the shipping price and doll fees though. https://www.pine64.org/rockpro64/ https://www.pine64.org/rockpro64/
- netsharc 4y agoBrowser engines need a lot of computing to know what color each pixel of a page needs to be, for each pixel: the typeface affects it, the background image of all the parent elements (in case of transparency) affects it, the CSS positioning of the elements affects it (there could be a white title text, but an annoying cookie popup with a semi-dark background means it needs to be displayed as a greyed out text).
- colechristensen 4y agoThey really don't though, they could do it just fine in 1995. Browsers have bloated into crazy complex machines though that do way more than rendering some text and graphics. The simple rendering is not why browsers are slow on RPis.
- leros 4y agoHTML is simple. Add CSS and dynamic DOM manipulation and it's whole different situation.
- colechristensen 4y agoThe javascript stuff that transformed hypertext documents into fully fledged applications is complicated. HTML and CSS really isn't. It's hard to have an unbiased opinion about what is easy and what is hard for a computer to do. Much of what is done on the web could be 90% as good with 10% of the complexity, but we're buried under too many layers of abstraction, bloat, and "improvement".
- rwalle 4y agoEnough of such comments. Obviously you have never worked much in the front end or the web user experience, and don't understand the complexity or the difficulty of such technologies. Anyone saying "things were fine in 1995" is ignoring how non-interactive, non-intuitive how web pages were, and how much more pleasant it is to look at a web page and get the information today. It is true that some web pages are using unnecessary (or even too much) animations and such and may have a negative effect on user experience or accessibility, but there is no doubt that the web is a better place than it was in 1995. And I'm sorry to say that your personal opinion does not matter, and the web is never going back to 1995.
- leros 4y agoI played around a lot and never got it to improve. I think it's just limited compute resources on the Pi and the fact that web browsers and websites have become massive. It takes a lot to a render a webpage these days. It might have been lack of GPU. Moving windows around the screen was also really painful, probably 1-2 fps render rate as I dragged. I know browsers off-load a lot to GPUs these days too, so that could explain the slow browser rendering.