#gigabytes — Public Fediverse posts on home.social

Hacker News @[email protected] · 2026-01-17 · 09:56 UTC

Streaming gigabyte medical images from S3 without downloading them

https://github.com/PABannier/WSIStreamer

#HackerNews #Streaming #Medical #Images #S3 #Gigabytes #WSIStreamer #TechInnovation

#hackernews #streaming #medical #images #s3 #gigabytes

Hacker News @[email protected] · 2026-01-17 · 09:56 UTC

Streaming gigabyte medical images from S3 without downloading them

https://github.com/PABannier/WSIStreamer

#HackerNews #Streaming #Medical #Images #S3 #Gigabytes #WSIStreamer #TechInnovation

#hackernews #streaming #medical #images #s3 #gigabytes

C. @[email protected] · 2024-12-01 · 22:04 UTC

With our modern #computing technology -- desktop #computers with 8 or more CPU cores, each running at multiple #gigahertz, executing a sum total of many billions of instructions per second, with memory measured in double-digit #gigabytes, blindingly fast main storage from SSDS -- I am always continually amazed that #slow #software even exists.

I'm not talking about something where extended calculations genuinely tie up the processor for an arbitrary length of time. I mean, "this program takes a seeming age just to do X".

I was reminded of this again yesterday. Audacity, the audio-editing program, takes about 10s from clicking the icon to it showing a window (on a Linux x86_64 PC). This isn't opening a project or any data files; it's just to get the program initialized to a state where you can see the UI.

And that's the cache-hot behaviour on this machine, which isn't slow.

What the heck is #Audacity doing in those 10s? If the answer is "loading plugins", I'd again point out that this is sufficient time to load many gigabytes of data from SSD, open and read hundreds of files, , and execute many billions of CPU instructions, with time left over. I don't buy this as a legitimate explanation.

#SlowSoftware #waiting

#computing #computers #gigahertz #gigabytes #slow #software

C. @[email protected] · 2024-12-01 · 22:04 UTC

With our modern #computing technology -- desktop #computers with 8 or more CPU cores, each running at multiple #gigahertz, executing a sum total of many billions of instructions per second, with memory measured in double-digit #gigabytes, blindingly fast main storage from SSDS -- I am always continually amazed that #slow #software even exists.

I'm not talking about something where extended calculations genuinely tie up the processor for an arbitrary length of time. I mean, "this program takes a seeming age just to do X".

I was reminded of this again yesterday. Audacity, the audio-editing program, takes about 10s from clicking the icon to it showing a window (on a Linux x86_64 PC). This isn't opening a project or any data files; it's just to get the program initialized to a state where you can see the UI.

And that's the cache-hot behaviour on this machine, which isn't slow.

What the heck is #Audacity doing in those 10s? If the answer is "loading plugins", I'd again point out that this is sufficient time to load many gigabytes of data from SSD, open and read hundreds of files, , and execute many billions of CPU instructions, with time left over. I don't buy this as a legitimate explanation.

#SlowSoftware #waiting

#computing #computers #gigahertz #gigabytes #slow #software

Smol Bean @[email protected] · 2023-11-22 · 19:07 UTC

So a gigabyte is unfortunately a terrible way of measuring bytes because giga* is base10 (1000 bytes/decimal) and bytes are base2(binary) , so the standard was changed to gibibytes because it would be base2 (1024 bytes) but we got so used to the word "gigabyte" (probably because of the metric system) that we still use it to mean base2 despite it technically meaning base10.

Because of that, storage makers advertise their products as gigabytes because it makes it seem bigger than it actually holds (in gibibytes) and it is legally true.

How can society switch to using the word gibibytes so computing data is less confusing and more readable. It probably starts with retraining ourselves to use gibibytes even if it feels weird.

What are your thoughts?

#Computing #Data #MetricSystem #Binary #Tech #Technology #Standardisation #Gigabytes #Gigabyte #Gibibytes #Gibibyte

#computing #data #metricsystem #binary #tech #technology

Smol Bean [OLD] (moved to https://evil.social/@shrimple) @[email protected] · 2023-11-22 · 19:07 UTC

So a gigabyte is unfortunately a terrible way of measuring bytes because giga* is base10 (1000 bytes/decimal) and bytes are base2(binary) , so the standard was changed to gibibytes because it would be base2 (1024 bytes) but we got so used to the word "gigabyte" (probably because of the metric system) that we still use it to mean base2 despite it technically meaning base10.

Because of that, storage makers advertise their products as gigabytes because it makes it seem bigger than it actually holds (in gibibytes) and it is legally true.

How can society switch to using the word gibibytes so computing data is less confusing and more readable. It probably starts with retraining ourselves to use gibibytes even if it feels weird.

What are your thoughts?

#Computing #Data #MetricSystem #Binary #Tech #Technology #Standardisation #Gigabytes #Gigabyte #Gibibytes #Gibibyte

#computing #data #metricsystem #binary #tech #technology

Link @[email protected] · 2023-08-22 · 09:34 UTC

As awful as #ASUS motherboards are, #GIGABYTE’s are 10x worse, at least their #AORUS line. No video signal, No Wi-Fi until performing a full power cycle, PC shutting down when attempting a BIOS update - literally experienced all the worst case scenarios on their motherboard and other customers on their forum have all stated the same damn experience. For some reason, I think I’ve had the least problems (not zero) with #ASRock’s, and yes what’s with these Taiwanese brands having (almost) fully capitalised names.

#asus #gigabytes #aorus #asrocks