If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#16
|
|||
|
|||
Win7 Registry Size
In message , Rene Lamontagne
writes: On 12/05/2017 7:04 AM, Ed Cryer wrote: [] Well you fellows got my curiosity up about registry cleaners. I have never used one, So having a 1 day old Macrium backup I decided to have a look. I exported the registry to a blank folder and checked it's size it was 377 MB. Ran Ccleaner registry cleaner and it took 4 passes before it reported no errors' Exported it again and found the new clean size to be(drum roll) 383 MB! [] Case Closed. Rene Maybe Ccleaner has done you a favour. I've never seen it do multiple passes, and I'd guess it was repairing something that might have been about to crash your system. 6MB added to shore up a shaky wall. Ed I dunno Ed, I have never used a registry cleaner and this was just an experiment to see what happened but I always assumed they were supposed to remove overburden. This system has always been quick and smart and using this registry cleaner doesn't seemed to have hurt or helped it any, I'm just very surprised that it added instead of subtracting. Rene It's also possible that it would have gone from 377 to 383 MB during that session even if you _hadn't_ run the cleaner - in other words, the increase may not be due to the cleaner. I'd suspect it wasn't, in fact; we can argue for ever as to whether cleaners do any good or actually do harm, but I don't think they will _increase_ it. The defragger someone mentioned, now that sounds as if it should be both worthwhile and harmless, if the registry is really a file system (an obfuscated one, as Paul puts it). I've _never_ thought the registry a good idea. Common libraries, i. e. the .DLL system, yes (though that has its problems when backward compatibility is compromised), but - apart from the undetectable advantage of loading from RAM rather than disc - I've never seen its advantage over .ini files, for software settings. -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf Feudalism : It's your count that votes. |
Ads |
#17
|
|||
|
|||
Win7 Registry Size (Win 10)
On 05/12/2017 16:09, Rene Lamontagne wrote:
On 12/05/2017 9:33 AM, Rene Lamontagne wrote: IT now reads 618 MBs!!!! Checked again, now back to 384 MBs. As at least one other has advised, the registry is held natively in a binary format, but choosing File, Export will export the selected key in text format. AFAICR, in XP-, you used to be able to read off, and if required limit, the current registry size, in its native binary format, by rt-click-ing My Computer, and choosing Properties, Advanced, Performance, to take you into the Virtual Memory and Paging settings, but that subsection controlling the Registry has disappeared from Vista+. I don't know how you find out the true binary registry size in in W7 other than, as others have suggested, adding up the sizes of the component files. In W7, The registry natively exports in UTF-16, which in simple terms is two bytes per character, but some text editors may 'transparently' convert this to, in decreasing order of probability, ANSI, UTF-8, or ASCII/DOS all of which use only 1 byte per character. Further, they may do this on loading the file when it is opened, or upon saving it when it has been changed. Hence the apparent doubling of size could simply be due to the program you used to open it, or whether you made any changes to it, even an unintentional one such as inserting a blank line by pressing Return. |
#18
|
|||
|
|||
Win7 Registry Size (Win 10)
"Java Jive" wrote
| AFAICR, in XP-, you used to be able to read off, and if required limit, | the current registry size, in its native binary format, by | rt-click-ing My Computer, and choosing Properties, Advanced, | Performance, to take you into the Virtual Memory and Paging settings, | but that subsection controlling the Registry has disappeared from | Vista+. I've never seen what you describe. I use the XP paging settings to put a fixed-sized swap file on a different partition and block any swap file from C drive. But there's nothing there about the Registry. I wouldn't see the point, anyway. Why would anyone limit the size? Anything written there would be written for a purpose. It processes were suddenly blocked due to size limits the system would begin to act unstable in numerous ways. I don't know how you find out the true binary registry size in | in W7 other than, as others have suggested, adding up the sizes of the | component files. | | In W7, The registry natively exports in UTF-16, which in simple terms is | two bytes per character, but some text editors may 'transparently' | convert this to, in decreasing order of probability, ANSI, UTF-8, or | ASCII/DOS all of which use only 1 byte per character. Further, they may | do this on loading the file when it is opened, or upon saving it when it | has been changed. Hence the apparent doubling of size could simply be | due to the program you used to open it, or whether you made any changes | to it, even an unintentional one such as inserting a blank line by | pressing Return. |
#19
|
|||
|
|||
Win7 Registry Size (Win 10)
On 06/12/2017 14:08, Mayayana wrote:
"Java Jive" wrote | AFAICR, in XP-, you used to be able to read off, and if required limit, | the current registry size, in its native binary format, by | rt-click-ing My Computer, and choosing Properties, Advanced, | Performance, to take you into the Virtual Memory and Paging settings, | but that subsection controlling the Registry has disappeared from | Vista+. I've never seen what you describe. I said AFAICR because I was then in too much of a hurry to check this (washing machine flood), but, having now done so, the first line of my paragraph quoted above should have read: In Win2k-, you used to be able to read off, and if required limit ... It's there in W2k-, but, as you rightly point out, not in XP+. |
#20
|
|||
|
|||
Win7 Registry Size (Win 10)
"Java Jive" wrote
| I said AFAICR because I was then in too much of a hurry to check this | (washing machine flood), but, having now done so, the first line of my | paragraph quoted above should have read: | | In Win2k-, you used to be able to read off, and if required limit ... | | It's there in W2k-, but, as you rightly point out, not in XP+. Odd. I wonder why they removed it.... Or why they ever had it, for that matter. But either way, it's certainly less important than water filling up your cellar. Good luck with the flood. |
#21
|
|||
|
|||
Win7 Registry Size
"Mayayana"
news alt.windows7.general, wrote: "Rene Lamontagne" wrote | I exported the registry to a blank folder and checked it's size | it was 377 MB. As Paul said, the Registry is files. If you export to .reg files you're creating a text-based record that can be used to import that data again. It won't be the same size because it's a text file and the Registry is a database. In other words, what you export is comparable to a CSV file. Also, Registry cleaners usually focus on a few things. Most notably entries under HKCR for COM libraries that may be gone. There may also be entries for uninstalled software. But those entries are a tiny portion of the total Registry. They're harmless. And in some cases they may be useful: If you decide to reinstall a program later you might be glad your settings are still there. Sysinternals used to have a program to defrag the Registry. I don't know if it still exists or whether such a task would still be useful, but it seems a defrag would make more sense than just removing a handful of entries. ERUNT includes NTREGOPT...doesn't 'defrag' the registry, but does compact it. Removes old entries marked for deletion, essentially. -- Please visit our moderators personal page: https://tekrider.net/pages/david-brooks-stalker.php Now for a cheeky message from our sponsors: The door is the key. |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|