5 ms·
Sometimes I miss being able to hear the hard disk read heads moving around. It was a surprisingly accurate way to tell what your computer was up to. Someone mus
by modeless 6y ago
Sometimes I miss being able to hear the hard disk read heads moving around. It was a surprisingly accurate way to tell what your computer was up to. Someone must have made a simulation of this, right?
- marmshallow 6y agoI was just thinking about this. Other examples that come to mind are reading CD/DVDs, dial up modems, and turning on old CRT monitors
- pabo 6y agoThere's an anecdote about Jim Gray: he was once asked by a company to help troubleshoot a performance issue in their database (this was in the 80s or 90s I guess). Surprisingly, he did not start by looking at any code, but went directly to the server room and listened carefully for a while. Then, he said what the problem was. (IIRC it was an issue with wrong/missing indexes.) They went to look at the code, and it turned out he was right. Everyone was astonished, how he did this. He was "merely" listening to the sound of the spinning disks while the problematic queries were running.
- ponker 6y agoWhether these stories are true or false I love them.
- pabo 6y agoOk, I found the reference for this story [1]! It turns out I messed up some details, but the core of the story is true. (It was not a company but Alex Szalay [2] at JHU, and it was not an indexing but a layout issue.) Jim asked about our "20 queries," his incisive way of learning about an application, as a deceptively simple way to jump-start a dialogue between him (a database expert) and me (an astronomer or any scientist). Jim said, "Give me your 20 most important questions you would like to ask of your data system and I will design the system for you. " It was amazing to watch how well this simple heuristic approach, combined with Jim's imagination, worked to produce quick results. Jim then came to Baltimore to look over our computer room and within 30 seconds declared, with a grin, we had the wrong database layout. My colleagues and I were stunned. Jim explained later that he listened to the sounds the machines were making as they operated; the disks rattled too much, telling him there was too much random disk access. We began mapping SDSS database hardware requirements, projecting that in order to achieve acceptable performance with a 1TB data set we would need a GB/sec sequential read speed from the disks, translating to about 20 servers at the time. Jim was a firm believer in using "bricks," or the cheapest, simplest building blocks money could buy. We started experimenting with low-level disk IO on our inexpensive Dell servers, and our disks were soon much quieter and performing more efficiently. [1] https://cacm.acm.org/magazines/2008/11/549-jim-gray-astronomer/ https://cacm.acm.org/magazines/2008/11/549-jim-gray-astronom... [2] https://en.wikipedia.org/wiki/Alex_Szalay https://en.wikipedia.org/wiki/Alex_Szalay
- sneak 6y agoAnother classic you’ve probably already read but linking it in case you haven’t: http://catb.org/jargon/html/magic-story.html http://catb.org/jargon/html/magic-story.html
- deleted 6y ago[deleted]
- EdwardDiego 6y agoI remember being acutely sensitive to the sound of a good floppy being read vs. a bad floppy when I was getting into computers. Likewise being able to hear if you and the BBS were properly connecting or not. Hearing your modem retry the handshake after dialling 90 times to get into a popular one was heartbreaking.
- SergeAx 6y agoWhen playing with Agat, Soviet Apple II clone, I've altered couple of bytes in RWTS (reat/write track/sector) routine from nop;nop; to clicking sound. That way I got gentle rattle wheh floppy was reading/writing okay and pauses when something was going wrong. Later I've found out that piece of code was written by Wozniak himself.
- throwaway_pdp09 6y agoI have old spinny disks and it is a VERY, VERY simple and useful feedback for DB work to hear it fighting itself. As an aside I get the feeling software is being written more and more to assume SSDs. Starting up visual studio from fresh on my machine will thrash the disk. Disk read is roughly (average) 2MB/sec throughout. Disk queue length will hit 10 several times. It takes 4 mins 50 secs (290 seconds) before the disk will calm down - I just timed it. Total mem for the process when all's finished - 204MB! That's all! My feeling is the VS code is spawning many threads which are each fighting each other for the disk. It's really, really poor.
- GordonS 6y agoWhile Visual Studio is undoubtedly a great IDE, it's biggest issue for me always been performance, especially when paired with ReSharper - this has been the case even before SSDs were ubiquitous. Honestly, I'd strongly recommend you get an SSD - prices are really cheap nowadays.
- throwaway_pdp09 6y agoIs VS a great IDE. It's laggy, it's too 'helpful' eg. it's going to add a close bracket if you type an open bracket unless you tell it not to, in which case it's a bitch to customise (took me 20 mins to find that option) and no luck so far if I want to adjust eg. menu & tab font to make them larger. It can do refactoring etc. and has context-sensitive help/completions but honestly I work in emacs because it offers so much more - except the high-level refactoring etc. Omnisharp works, sort of... VS just isn't as good as emacs in many, many basic ways. Anyway, I'll look at SSDs and stop nattering about editors.
- GordonS 6y agoI do think it's a great IDE, apart from the lag - though that is obviously a big issue. In fact, after working with VS for years and getting more and more annoyed by the lag, I tried JetBrains Rider - I'm a total convert, it's one of my favourite ever pieces of software! The UI takes a bit of getting used to if you've been using VS for a long time, but not that much. Plus there's an excellent dark theme that is quite close to VS's. Rider is absolutely stuffed with features and config switches - it's close to feature parity with VS, with VS able to do a few things Rider can't, and vice-versa. Rider absolutely flies by comparison to VS, and is more stable too. Oh, and edit-and-continue "just works" in Rider, whereas I've always found it problematic in VS. After getting an SSD, trying Rider is my next suggestion :)
- 7373737373 6y agoI randomly saw a poster for this paper: http://www.ise.tu-berlin.de/fileadmin/fg308/publications/2017/2017-bermbach-audiocues.pdf http://www.ise.tu-berlin.de/fileadmin/fg308/publications/201... which implements something like it! Demonstration: https://www.youtube.com/watch?v=gWJtGZOp3K0 https://www.youtube.com/watch?v=gWJtGZOp3K0 https://github.com/dbermbach/audiocues https://github.com/dbermbach/audiocues
- RhysU 6y agoScooped back in 2000, if not before: > We created a network monitoring system, Peep, that replaces visual monitoring with a sonic `ecology' of natural sounds, where each kind of sound represents a specific kind of network event. https://www.usenix.org/legacy/publications/library/proceedings/lisa2000/full_papers/gilfix/gilfix_html/index.html https://www.usenix.org/legacy/publications/library/proceedin...
- verytrivial 6y agoThe Vice emulator for the 1541 family of floppy drives has optional sound output. Throws you right back to the 80s!
- tinus_hn 6y agoYou could reprogram these drives to play songs by vibrating the heads
- blauditore 6y agoThis immediately came to my mind as well. Whenever the computer was growling, it was better to not mess with it and wait it out.
- svnpenn 6y agohttps://en.wikipedia.org/wiki/Resource_Monitor https://en.wikipedia.org/wiki/Resource_Monitor
- remar 6y agoI've been meaning to get around to basically plagiarizing this UI for a personal linux system monitoring tool. I've tried a bunch of the popular linux disk/resource usage monitors but I find none are as flexible/nice to look at as Windows' Task Manager overview graphs and Resource Monitor. Any time I'm using a Windows system I will dedicate a monitor to just having Resource Monitor's disk usage tab open (although it can result in nontrivial CPU usage under certain disk access patterns).