Hacker Newsnew | past | comments | ask | show | jobs | submit | janvdberg's commentslogin

Yes, this is unfortunately my experience with GoAccess


Im sorry for your loss Matt.


Awesome to find DFW content on HN!

Love this piece!

I will surely blog about it on davidfosterwallace.nl in the coming weeks (it'll be in Dutch though).


Oh thanks! That'll be great to see :). Edit: feel free to drop a link here or send to me when it's ready, I'd love to read it! My contact info is in my blog!


Does anybody know the specific keyboard make/model/type? Doesn't look like a foldable from the image?



OP mentions "Logitech Pop" at the end of the article.


I have this specific keyboard, "POP Icon Keys" (not to be confused with "POP Keys"). It's fine. I can confirm that it doesn't fold and is not particularly compact.


I love the talk! But I do feel something critical is missing. You can not talk about semi-conductors without at least mentioning Walter Schottky (but I think that doesn't fit the narrative because he was a German).


The theories from before WWII of Walter Schottky were indeed an important step in the development of semiconductor physics.

Besides Schottky there are a great number of other people who had critical contributions towards the development of semiconductor devices and who are not mentioned in the very short summary from the video.

For instance, Julius Edgar Lilienfeld had invented before WWII 2 kinds of field-effect transistors: metal-semiconductor FETs and depletion-mode MOSFETs. But before WWII making such devices was not reproducible, because the available semiconductor materials were too impure.

Nevertheless, the Bell team searching for methods to make semiconductor triodes was aware of these patents and they were stimulated by them to find alternative structures that worked.

The work of the team that discovered the point-contact transistor would have been completely impossible without the techniques developed during the war by some of their colleagues, e.g. by Russell Shoemaker Ohl, for making pure germanium and silicon and diodes using these materials. (During the war, Ohl has also invented the silicon solar cell, as a byproduct of the work on radar diodes.)


Thank you! And Schottky was a good catch, and there are a few European scientists I’m not paying appropriate homage to, for sure. I had to cut a lot to get this down to a 30 minute talk, to native Kazakh speakers, so I definitely tightened up a lot. I will go back and read on Schottky again.


Side-note, for those interested, I want to point out a new CMS: https://pureblog.org/ Not a SSG in the strict sense, but it generates md files and serves those on the fly.

There is a WordPress migrate-tool that worked flawlessly.


I tried changing it, but I guess when a post hits the fp this is not possible anymore (only by mods).


It's not affected by hitting the FP but the edit window is 2 hours. I've edited it now. Sorry I didn't see this earlier!


Dutch daily blog: https://janvandenberg.blog/



My first command is always 'w'. And I always urge young engineers to do the same.

There is no shorter command to show uptime, load averages (1/5/15 minutes), logged in users. Essential for quick system health checks!


It should also be mentioned, Linux Load Average is a complex beast[1]. However, a general rule of thumb that works for most environments is:

You always want the load average to be less than the total number of CPU cores. If higher, you're likely experiencing a lot of waits and context switching.

[1] https://www.brendangregg.com/blog/2017-08-08/linux-load-aver...


On Linux this is not true, on an IO heavy system - with lots of synchronous I/Os done concurrently by many threads - your load average may be well over the number of CPUs, without having a CPU shortage. Say, you have 16 CPUs, load avg is 20, but only 10 threads out of 20 are in Runnable (R) mode on average, and the other 10 are in Uninterruptible sleep (D) mode. You don't have a CPU shortage in this case.

Note that synchronous I/O completion checks for previously submitted asynchronous I/Os (both with libaio and io_uring) do not contribute to system load as they sleep in the interruptible sleep (S) mode.

That's why I tend to break down the system load (demand) by the sleep type, system call and wchan/kernel stack location when possible. I've written about the techniques and one extreme scenario ("system load in thousands, little CPU usage") here:

https://tanelpoder.com/posts/high-system-load-low-cpu-utiliz...


Hey Tanel - I wanted to thank you for that blog post and psn tool - it recently helped me in a tricky performance investigation.


Glad to be helpful! :-)


The proper way is to have a idea of what it normally is before you need to troubleshoot issues.

What is a 'good load' depends on the application and how it works. Some servers something close to 0 is a good thing. Other servers a 10 or lower means something is seriously wrong.

Of course if you don't know what is a 'good' number or you are trying to optimize a application and looking for bottlenecks then it is time to reach for different tools.


Glances is nice. I think it is a clone of HP-UX Glance.

https://nicolargo.github.io/glances/

I have also hacked basic top to add database login details to server processes.


Me too! So much so that I add it to my .bashrc everywhere.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: