Live data from Hacker News

24-core CPU and I can’t type an email

randomascii.wordpress.com

131–140 of 320 posts

Re: 24-core CPU and I can’t type an email

#132
post #36

Earlier quoted context omitted.

I usually append /h/ to the URL (/mail/h/) and get a HTML version. It can work even without JS and it has classic design with small rows that works well on my small screen. No Material Design and no huge elements with large offsets.

I hate material design. I don't want more vacant space, I want density. Ive always loved Japanese website layouts. Content is beauty.

I hope you have noticed that in GMail you can swtich between different "density" modes. In your Inbox, click on the cogwheel on the right-hand top corner and select the second option "Display density". The "Compact" setting is actually rather dense. Although, it mostly affects the density of rows (conversations) in your inbox and does not scale e.g. the search box input field above.

Re: 24-core CPU and I can’t type an email

#135
So why are we in this mess? Because there are still buffer overflows.

Address space randomization is done because buffer overflows allow exploits. But rather than fixing the underlying problem, we now have complex schemes to spread programs over the entire 64 bit address space to make such exploits unreliable.

Then, apparently Microsoft's Javascript JIT engine has enough problems with buffer overflows that each compiled program is in a different random part of the address space to try to prevent Javascript exploits.

Re: 24-core CPU and I can’t type an email

#136

Earlier quoted context omitted.

I'm running Gnome and for the most part it has been excellent; Linux in general, though, still has a lot of trouble maintaining good UI speed at the same time as I/O throughput. I'm on Fedora, and dnf/rpm is an excellent example - even though I'm on an SSD, I can tell when something is updating in the background because stuff will lag for a little while. It feels like this has been a problem forever, and while it has…

> while it has definitely improved over time it's still not really possible to say, in a simple way, "I care more about interactivity than other stuff, prioritise that that's not what mainline kernel optimizes for, you have to use liquorix or another kernel ( https://liquorix.net/ )

You would assume that big guys like RedHat would already have done this for you.

Re: 24-core CPU and I can’t type an email

#137

Have to give it to Apple for acknowledging the difficulty in writing responsive (as in no lockups) applications and designing multiple developer framework solutions to solve it (Grand Central Dispatch and NSOperationQueue). Both those are designed to enable developers to easily offload work to background threads and prioritise queued work for the user. No open-for-interpretation thread priorities, but named QoS prior…

Maybe more developers would make use of it if it was open source, existed for other platforms, and available for languages people actually use on those other platforms.

Re: 24-core CPU and I can’t type an email

#139
post #56
post #46

I just kind of figured we'd stop having UI lag by now. I work on a 24 core workstation with 64GB of RAM and things lag all the time. Not slow to complete, like jittery key entry and non-responses. Haven't we figured out thread prioritization by now? Can't we make sure something draws 60 times per second while things are going on in the background? My Android Studio build should be totally isolated from my inbox. I kn…

I have a similar workstation (though 12 core I think) and recently I've thought about just running entirely separate VMs, each with dedicated cores and RAM. I'm sick of random slowdowns like you mentioned.

I think qubes os could be a good fit for that workflow

Re: 24-core CPU and I can’t type an email

#140
post #35

Interesting story in particular, but in general, performance and memory behave like any other resource that is plentiful: they get used up until things are slowish again. Like road space. Things get added on top of each other until the reduction in speed becomes visible. Because these days, unlike in the 90's, it's no help waiting for the next Pentium processor to come out this usually results in a heavy optimisation…

The move from CRT to LCD adds a few milliseconds depending on the screen. We're so used do it by now, that typing on old hardware is almost jarring. It feels almost TOO responsive.
Post reply on HN