|
I don't even necessarily mean for disk cache, but as something.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
I think they just changed it so it doesn't appear that way anymore.
It still predictively loads things into RAM but the presentation is different so it doesn't appear that RAM is used.
I think they changed that because people were like "WTF MSFT WHY USE ALL MY RAM?!"
It takes almost nothing for the OS to chuck it and use it for whatever is actually needed instead of what it predicted if it got it wrong.
|
|
|
|
|
That's generally correct. My system shows 5 GB available RAM right now; however, the majority of that should be freed pages which point to disk files (including application code) so that if the file (application) is (re)opened, it doesn't need to be read from disk. A small portion (128MB) is zeroed pages, just enough that when an application asks for a blank memory page it can be delivered instantly without waiting to zero it.
Windows also has a mechanism for pre-loading pages it expects to need shortly (mostly used during boot which is more predictable) and .NET has similar mechanisms for pre-loading code before it's needed (although it typically requires running optimization tooling to build the pre-loading list, which major apps like VS do but many don't).
There's a number of other apps that have 'fast load' setups to pre-load the memory their application uses; however, I often find them annoying as they may pre-load their application even though I have no intention of using it that day...
|
|
|
|
|
I am having the same relationship to my car.
When I am not driving it, its total utilization is falling, so I keep it running as much as possible.
I pick up four friends to go with me on trips, to utilize the seat capacity as much as possible.
To utilize the engine to the maximum extent we have to go out on the highway (otherwise we would break the speed limit all the time).
This part of the year, I am happy about the utilization factor of the headlights; I keep them on at all times to rise utilization.
Also, with lots of rain, the windshield wipers is another component that can contribute to the total utilization.
Obviously, the car stereo is active all the time, to make sure it is utilized to the fullest extent possible.
Making the maximum possible use of everything you have at your disposition is essential for a good life. Keep your fridge and freezer filled up to utilize its capacity. If you have spare beds in your home, invite someone to sleep in them. Keep all your electric lights at maximum utilization. Maybe even your SO!
|
|
|
|
|
I think you may be having a laugh at me, I'm not sure.  But either way, I agree with parts of what you wrote.
trønderen wrote: If you have spare beds in your home, invite someone to sleep in them.
I used to do this when I was younger and could get away with it. I was a homeless teenager, so when i was in my twenties and living in seattle among a sea of homeless young adults, I'd let them crash where I lived. I lost some stuff to theft, and a little peace to some drama, but I'm still glad I did it. Because once or twice I met someone who did that for others, when I needed a place to stay.
Imagine a world where people with more than they need were very open to sharing their excess with others.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
honey the codewitch wrote: Assuming you're going to be using your machine in the near future, your I/O may be sitting idle, but ideally it would be preloading things you were planning to use, so it could launch faster.
That's all fine and dandy when it knows what it is I'm going to be using, but making the wrong guess means someone's expended resources to do that work for nothing. Leaving less memory for other things that could've been cached.
It's really all a balancing act, every OS has its own guidelines explaining what each app should do or avoid in order to be a good citizen. Then it's up to the OS to juggle it all and try to make the correct guesses.
Bottom line, I'm with you, if you have the resources, by all means, use them. But the key, as already mentioned, is that you have to be smart about it, you can't act as if you're the only one around, 'cuz everybody else is trying to do the same...
|
|
|
|
|
Of course, and by ideally, I am indeed intending a hypothetical scenario with ideal conditions, as illustrative of a point, rather than an attempt to reflect reality.
That point is that if you can get your I/O to do useful work when it's not doing anything else, that is typically a net win.
Even if you can't, as long as you win more times than you lose, it's still a win - like blackjack and card counting, if you do it right, you'll win a lot.
But again, these situations are only intended as illustrative hypotheticals, and broadly articulated ones at that. I didn't want to get lost in the weeds.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Sure. Cache hit is a thing, and so is cache miss. It doesn't mean we shouldn't try to cache anything at all. Just that the algorithm used to decide what to cache vs what to let go of is very much something that's still in development. I'm not aware of any magic bullet.
|
|
|
|
|
There isn't really. It's all highly situational.
For example, I do dithering and automatic color matching in my graphics library so that I can load a full color JPG on to for example, a 7-color e-paper display. It will match any red it gets, with the nearest red that the e-paper can support and then if possible, dither it with another color to get it closer.
It takes time. I cache the color matching and dithering results in a hash table as I load the page. The hit rate is extremely high. It's very rare that a pixel of a particular color only appears once. That's close to ideal. The cache is discarded all at once once the frame is rendered. In that case, also easy to determine.
Naturally, for a web site, things look much different, and considerations change. Your cache hit algo probably won't be as ideal as my previous example just because there are so few examples in life that closely match a general algorithm's design.
At the end of the day though, you don't need a silver bullet to make it worthwhile, luckily for us - you just need to win more than you lose, once all the chips are counted.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
honey the codewitch wrote: At the end of the day though, you don't need a silver bullet to make it worthwhile, luckily for us - you just need to win more than you lose, once all the chips are counted.
This. So much this.
|
|
|
|
|
honey the codewitch wrote: When your CPU core(s) aren't performing tasks, they are idle hands.
When your RAM is not allocated, it's doing no useful work. (Still drawing power though!)
While your I/O was idle, it could have been preloading something for you.
Sounds like the wife complaining about her hubby.
|
|
|
|
|
Anything above 80-85% utilization will quickly start thrashing that particular resource. Up to that point you're spot on.
|
|
|
|
|
I wouldn't say *anything*, but I do hear you.
Certainly thrashing is a concern with something like virtual memory, but I'm not even necessarily talking about vmem here. With the memory example, my point was simply about a hypothetical ideal. It takes the same amount of power to run 32GB of allocated memory as it does 32GB of unallocated memory, so if you're not using that memory for something, it's in effect, being wasted. In the standard case, this would be an OS responsibility, and if an OS wanted to approach that ideal, it might use something, like an internal ramdisk to preload commonly used apps and data for example. May as well. It's not being used for anything else, and if you run out, you just start dumping all your ramdisk. Only after it's gone, start going to vmem. Something like that. It's just an idea, there are a million ways to use RAM.
I/O (to storage) is really where your thrashing occurs, and historically there was literal thrashing due to the moving parts involved, even though that's so often not the case anymore.
But again, the idea would be in an ideal "typical" situation, an OS would manage that, and run any preloads at idle time, and make them lower priority than anything else.
In effect, as long as everything you're doing on top of idling is basically "disposable" thrashing won't be much of a concern.
The CPU is a bit of an animal, in that you'll need about 10% of it to run the scheduler effectively, and without that, everything else falls apart. So yeah, with a CPU it's more like 80-90% utilization, although 100% is acceptable for bursts. In any case, I worded my post carefully to dictate that the CPU should be utilized when it has something to do. It's not the case that I'd necessarily want to "find" things to do with it the way I would with RAM. It's that when it does need to do something, it expands like a lil puffer fish and uses all of its threading power toward a task - again, ideal scenario. The reason for the discrepancy here, vs say with RAM is because of power concerns. RAM uses the same power regardless. A CPU varies with task so it should be allowed to idle if that makes sense.
I hope this clears things up rather than making it worse.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
|
Maybe I'm misinformed, or maybe DDR5 does something previous RAM doesn't to save power. Neither would surprise me.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
I am pretty sure all RAM requires more energy to read/write than to just be powered up. Similar to a SSD or NVME drive
|
|
|
|
|
My understanding is that DRAM needs constant periodic refresh voltage to maintain its data
Memory refresh - Wikipedia[^]
So it's not act of reading or writing like an NVMe. It works kind of like an LCD does, in that the charge is sent to the LCD panel over and over with whatever the data is at that point.
In effect, the writes are always happening regardless, at least to my understanding.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
The refresh occurs at a far lower frequency than the ordinary reading/writing. You can do several hundred r/w accesses for each refresh.
|
|
|
|
|
Ah, good to know.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Whenever you experience a bottleneck, inspect your system for other, significantly under-utilized resources, and be honest to yourself, saying: OK, I wasted too much resources on that, and on that! I could have done away with a lot less on those parts.
|
|
|
|
|
Sure, absolutely. Getting a utilization profile can uncover a lot about your system.
I actually had fun sourcing my PC components to be perfectly matched so that I didn't experience unavoidable bottlenecks in what I use it for. But it's more than that of course. That doesn't even cover the software angle.
Why is my zip decompression only using 30% of my I/O? is my CPU too slow? That sort of thing. It's interesting, too.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
When my AMD A4 / 8 GB RAM / 128 GB SSD rig suffered 100% CPU utilization / 99% RAM utilization for minutes (SQL, some Python) while my boss stood behind me, he asked that would I urgently need a new box. I've said no, because the company owners are happy now, we use every bit of the kit they provided us, no money invested in idle, quickly aging tech.
|
|
|
|
|
At one time I was interested in how a computer used resources
The learning curve was too great with no background in electrical engendering I gave up
and was just happy if it worked
BUT I remember reading about "Bank Switching"
So is this still a concept used in a personal computer today?
And if so is it good design to manage system resources on personal computers?
Quote: What's that old saw? Idle hands are the devil's playground. Your computer is like that.
Why ask a machine to run full tilt if it only needs 50% resource to do the job?
If the job gets bigger then or another job needs resource's there is a reserve.
If this an illogical thought process happy to hear why I should have stayed out of this conversation
|
|
|
|
|
Because there is usually more work a computer *could* be doing.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Choroid wrote: BUT I remember reading about "Bank Switching"
So is this still a concept used in a personal computer today?
No. 32 or 64 bit logical addressing removed the need for it.
The problem in the old PCs was the addressing range. Most single-chip CPUs were 8-bit, with 16 bit addresses, so they could only handle 2**16 = 64 Ki bytes of RAM; there was no way to identify any more. Then came the LIM standard for banking: You could set up your system with, say, 48 Ki plain RAM and the upper 16 Ki of the address space handled by a LIM card, providing several 16 Ki blocks (or "banks") of physical RAM, but you could use only one of them at a time. You had to tell the LIM card (through I/O instructions) which of the banks to enable.
You would usually put code, not data, in the banked part: In the un-banked (lower 48 Ki) part, you put a stub that is called from other places. This stub tells the LIM card to enable the right bank where the actual code is placed, and jump to the code address in that bank. If this function called functions in other banks, it would have to call via an unbanked stub to switch to the right bank. Upon return, the previous bank had to be enabled again, to let the caller continue. It did not lead to blazingly fast performance.
Catching data access through a similar stub is not that easy. You could, in an OO world have a object in unbanked RAM with huge data part banked RAM, the object knowing the bank number and address, and channeling all access to it through accessor functions (set, get), but OO was little known in the PC world at that time. I never saw anyone doing this.
LIM was a PC concept. On larger machines, you could see memory overlays, which was also based on routine stubs, but the stub would read a code block from disk into RAM, overwriting anything that was there. You had much more flexibility, but PC disks were so slow in those days that it would have been next to unusable.
You could say that bank switching is a relative of paging mechanisms. I know of at least one family of 16-bit minis providing 64 Ki words (128 Ki bytes) of address space to each user, but could handle up to 32 Mi bytes of physical RAM. So the 64 terminals hooked up to the mini could have their full address space resident in RAM, with no paging. When the CPU switched its attention from one user to another one, it replaced the page table contents to point to the new user's pages - not that different from telling the LIM board to switch to another bank.
You could also say that the 8086 solution, with its segment registers, is a close relative to banking: It allowed direct addressing of up to a mebibyte; this required the instruction to identify the segment register (a parallel to bank number) in every instruction, so it worked even for 'banked' data, not just instructions. (There is a well known quote from the discussions in one big company about how to split that mebibyte between operating system and user segments, and a famous industry leader was quoted for wanting 384 Ki of that space being reserved for the OS, the remaining 640 Ki should be enough for any user program running in 1 Mi of RAM.)
Today, almost every general-purpose machine has at least 32 bit address (4 Gi bytes), 64 bits is becoming the new standard. Then there is no need for neither banking nor overlaying. Rather, the paging system is used to pack the pieces of memory addresses that are actually used into a much smaller physical address space than the logical address space presents to the program.
For special purposes - almost all of it falls under 'embedded' - bit addresses are seen even today. No more than 6-7 years ago, I was working with an 8051, extended with banking hardware for four 16 Ki banks. I believe that chip is still available. (I moved on to another project, so I am not sure.)
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
