I have an old model laptop (Sony Vaio VGN-CR35G) and it has an intel core 2 duo T8100 processor. It runs on windows 10 and I want to use it for coding. It has two slots of ram and currently both has 1gb in it. I wanted to know if it is advisable for me to buy additional ram for it, and my problem is because it is an old model laptop aging for more or less a decade, I wanted to know it's maximum ram capacity. I did found some solution online saying that I can use cmd to see the information I needed using "wmic memphysical get maxcapacity" but it outputs zero value and I cannot be able to find the reason why. What should I do?
I try to do some research about this laptop model but I can't get much information since it is an old model. I expect to see some suggestions about what I can do to make it more usable.
Related
I ask this question because I'd like to know this from my kernel mode Windows driver.
I have some library code porting from user mode that has some accompanying stress test to run; that stress test code need to know when CPU is idle.
Simple googling shows no result, at least from first several pages.
you need use ZwQuerySystemInformation with SystemProcessorPerformanceInformation infoclass ( you got a array of SYSTEM_PROCESSOR_PERFORMANCE_INFORMATION structures on output)
I remember that, back in the days of the Commodore 64, I had a Reference Book showing me which part of memory was assigned to do what.
I was wondering if something of the likes was available for Mac OS X.
My iMac has a 1TB hard disk and I'd like to know where the free space is, which part is allocated to the display, etc.
Any resources where I could learn more about this subject would be helpful.
Thank you.
The hard disk is not "memory" in the sense you're thinking of. None of it is used for active apps, the display, etc...
You're thinking of ram, but on modern OSs that isn't divided by task like it may have been on past systems. Where things are located is dynamically assigned as needed, and intentionally randomized for security reasons (google for ASLR for the randomization).
If you go into the "Utilities" folder hidden in your Macintosh "/Applications" folder, you'll see an application named "Activity Monitor".
Open that, and you'll be able to see both memory usage (mine looks like this):
And disk usage looks like this:
Now these two views may look a little boring, or underwhelming, compared to what you might have seen with your Commodore 64 (or in my case, I was using a Trash-80 Color Computer).... but these screenshots are just a quick slice of data from about 10 seconds of looking at each view. If you leave the disk usage screen up for more than 10 seconds, you'll see the I/O ribbon gets more detailed with time. And there's probably more functionality hidden in there that I haven't even noticed yet. Try it out.
In previous versions of VTune, there was a program called dsep.exe, which could be used to periodically poll hardware counters (specifically related to DRAM reads/writes) from VTune. This allowed me to gather counter data about each instance in time, rather than one summary at the end.
Unfortunately, this tool has been deprecated in 64-bit operating systems. Does anyone know a way to periodically (e.g., every 1 sec) get hardware counter data from VTune (or another program in Windows)?
Thanks in advance for your help.
All right, I wasn't able to completely fix this issue, but I got pretty close.
The latest version of VTune saves all of the hardware counter data in a SQLite database (projectfolder/sqlite-db/dicer.db). Since you can't get all of the hardware counter data exported directly from the GUI, you can use a SQLite browser data to get to the data you need.
Most of the hardware data is stored in the pmu-data table, timestampped with some wonky version of a rdtsc call.
The NSProcessInfo class has two methods named processorCount and activeProcessorCount. The documentation is as unhelpful as possible as to what is the different between a processing core and an active processing core. Or, in other words: what counts as an inactive processing core for Cocoa?
It may be that OS X can shut down cores when the system is overloaded (to reduce temperature).
On older MacBooks, one core could shut down if the power cord was the only power source (no battery). (I can't find link for that one but I'm pretty sure that was the case for my 2007 white MacBook.)
Also, the hwprefs command line utility can enable/disable processors cores.
Most of the time, you really want the activeProcessorCount since it's what really represents the state of the machine.
Edit: hwprefs is gone in Lion, but you can access the same functionality with sysctl -n hw.ncpu
I run Windows 7 RC1, which uses the same WTM from Vista. When i look at the processes, there some columns I'm not sure what the differences are:
Memory - working set
Memory - private working set
Memory - commit size
can anyone tell me what they are?
From the following article, under the section Types of Memory Usage:
There are two main types of memory usage: working set and private working set. The private working set is the amount of memory used by a process that cannot be shared among other processes, while working set includes the memory shared by other processes.
That may sound confusing, so let’s try to simplify it a bit. Lets pretend that there are two kids who are coloring, and both of the kids have 5 of their own crayons. They decide to share some of their crayons so that they have more colors to choose from. When each child is asked how many crayons they used, both of them said they used 7 crayons, because they each shared 2 of their crayons.
The point of that metaphor is that one might assume that there were a total of 14 crayons if they didn’t know that the two kids were sharing, but in reality there were only 10 crayons available. Here is the rundown:
Working Set: This includes all of the shared crayons, so the total would be 14.
Private Working Set: This includes only the crayons that each child owns, and doesn’t reflect how many were actually used in each picture. The total is therefore 10.
This is a really good comparison to how memory is measured. Many applications reuse code that you already have on your system, because in the end it helps reduce the overall memory consumption. If you are viewing the working set memory usage you might get confused because all of your running processes might actually add up to more than the amount of RAM you have installed, which is the same problem we had with the crayon metaphor above. Naturally the working set will always be larger than the private working set.
Working set:
Working set is the subset of virtual pages that are resident in physical memory only; this will be a partial amount of pages from that process.
Private working set:
The private working set is the amount of memory used by a process that cannot be shared among other processes
Commit size:
Amount of virtual memory that is reserved for use by a process.
And at microsoft.com you can find more details about other memory types.
'Working Set' is the amount of memory that the process currently has in physical RAM. In other words, accessing any pages in the 'Working Set' will not cause a page fault since the page is in RAM.
As for the other two, I'm not 100% sure, probably 'Working Set' contains sharable memory, such as memory mapped files, and 'Private Working Set' contains only pages that the process can use and are not shareable.
Have look at this site and search for the speaker 'Dave Solomon'. There is an excellent webcast that he gave which explains about Windows memory, and he mentions working set, commit sizes, and other memory terms.
EDIT:
Those site links are indeed dead :(
Instead, you can search Google for
vimeo david solomon windows
Those same videos look to be available on Vimeo now, which is cool.
If you open the Resource Monitor from the WTM, mousing over the various column headings of the interesting process displays a pretty informative tool tip.
e.g.
Commit(KB): Amount of virtual memory reserved by the operating system for the process in KB.
etc.
This article at Microsoft seems to be the most detailed.
Edit Oct 2018: new link