File Details |
|
| File Size | 0.1 MB |
|---|---|
| License | Freeware |
| Operating System | Windows NT/Server 2003/Server 2008/Vista/XP |
| Date Added | November 25, 2008 |
| Total Downloads | 500 |
| Publisher | Bitsum LLC |
| Homepage | RegBench |
Publisher's Description
RegBench is a small utility to benchmark your system registry. It is a console mode utility and emits console and XML output, the latter of which can be shown in a web browser automatically. At present it does NOT have a GUI for general user use and it is in the ALPHA stage of development. If you are not familiar with console mode utilities, you are not advised to download this utility at present.
Latest Reviews
coolticker reviewed v0.17 Alpha on Nov 26, 2008
It works but ... how usefull it is to benchmark registry ???
I get about 15.000 keys per second on my PIII-1Ghz and what can I say is it fast is it slow ?
The problem is that this benchmark is mainly impacted by CPU speed as Hard Drive is nearly not used unless to load the hive itself and the second time you start the benchmark, then the hive is loaded from Windows's disk cache memory with no physical drive access so the second benchmark is slightly faster than the first call.
I don't think that registry fragmentation has an impact over performances because as it is loaded into memory, then it has no "seek access time" as for hard drives.
regards.
jcollake reviewed v0.16 Alpha Preview on Oct 10, 2008
I'll rate my own program a '4', I hope people find that reasonable enough.
I just wanted to respond to the previous comment: I am inclined to agree with you. Development of this application was an experiment.
I want to determine just how much of an effect fragmentation and excessive 'trash' in a registry hive have on performance. It might be that they have little to no effect, thus making these registry cleaning and defragmentation tools of less utility than we all thought. Or, maybe we end up proving their usefulness.
I would love to see users take the time to do some testing and report on Bitsum's forums about this. I am personally very curious.
I report access times because they seem most likely to be affected by an inefficient registry. They represent the time it tooks to find a registry key or value.. I'll probably add some more tests to emulate real world registry accesses (such as COM lookups and such).
As for reporting in fractions of a millisecond, I don't know any other way to report it.. end users will want some progress bar or something that indicates efficiency, but that's near impossible to do as the speed will vary for each system based mostly on its hardware capabilities.
DatabaseBen reviewed v0.16 Alpha Preview on Oct 9, 2008
credit must be provided for the time in developing this freeware and it works.
however, it is my opinion that the data it provides is of little use to regular folks, especially since it simply benchmarks access times and provides results in the .000ms.
coolticker reviewed v0.17 Alpha on Nov 26, 2008
It works but ... how usefull it is to benchmark registry ???
I get about 15.000 keys per second on my PIII-1Ghz and what can I say is it fast is it slow ?
The problem is that this benchmark is mainly impacted by CPU speed as Hard Drive is nearly not used unless to load the hive itself and the second time you start the benchmark, then the hive is loaded from Windows's disk cache memory with no physical drive access so the second benchmark is slightly faster than the first call.
I don't think that registry fragmentation has an impact over performances because as it is loaded into memory, then it has no "seek access time" as for hard drives.
regards.
jcollake reviewed v0.16 Alpha Preview on Oct 10, 2008
I'll rate my own program a '4', I hope people find that reasonable enough.
I just wanted to respond to the previous comment: I am inclined to agree with you. Development of this application was an experiment.
I want to determine just how much of an effect fragmentation and excessive 'trash' in a registry hive have on performance. It might be that they have little to no effect, thus making these registry cleaning and defragmentation tools of less utility than we all thought. Or, maybe we end up proving their usefulness.
I would love to see users take the time to do some testing and report on Bitsum's forums about this. I am personally very curious.
I report access times because they seem most likely to be affected by an inefficient registry. They represent the time it tooks to find a registry key or value.. I'll probably add some more tests to emulate real world registry accesses (such as COM lookups and such).
As for reporting in fractions of a millisecond, I don't know any other way to report it.. end users will want some progress bar or something that indicates efficiency, but that's near impossible to do as the speed will vary for each system based mostly on its hardware capabilities.
DatabaseBen reviewed v0.16 Alpha Preview on Oct 9, 2008
credit must be provided for the time in developing this freeware and it works.
however, it is my opinion that the data it provides is of little use to regular folks, especially since it simply benchmarks access times and provides results in the .000ms.