Persistent Hash

[AdminX]

Everything you might have wanted to know about Rybka III's Persistent Hash.

"In addition, users can share persistent hash files, so that user A can benefit from the analysis done by user B. Persistent hash files can also be merged, so that user A can benefit from analysis done separately by users B and C. These various scenarios are the topic of this document."

also:

"1) Set the [Persistent Hash Path] engine parameter to some path on your hard drive where you want the persistent hash file to be placed."

This is why I asked about Ramdisk in my earlier post. My only remaining question is, is there really a 2 GB limit for Persistent Hash? Waiting for Vas to answer ...

http://www.rybkachess.com/docs/Rybka_3_ ... t_hash.htm

[Marc MP]

Everything you might have wanted to know about Rybka III's Persistent Hash.

"In addition, users can share persistent hash files, so that user A can benefit from the analysis done by user B. Persistent hash files can also be merged, so that user A can benefit from analysis done separately by users B and C. These various scenarios are the topic of this document."

That looks like very convenient...

I recently came across a fully functional free ramdrive driver, for those interested: http://www.mydigitallife.info/2007/05/2 ... 03-server/

[AdminX]

Everything you might have wanted to know about Rybka III's Persistent Hash.

"In addition, users can share persistent hash files, so that user A can benefit from the analysis done by user B. Persistent hash files can also be merged, so that user A can benefit from analysis done separately by users B and C. These various scenarios are the topic of this document."

That looks like very convenient...

I recently came across a fully functional free ramdrive driver, for those interested: http://www.mydigitallife.info/2007/05/2 ... 03-server/

But the Driver is not 64-bit, I saw that also ... I even downloaded it and tried it, thats how I found out that it is only the 32-bit version. But hey, I am not going to hate on those with 32-bit.

[Marc MP]

Everything you might have wanted to know about Rybka III's Persistent Hash.

"In addition, users can share persistent hash files, so that user A can benefit from the analysis done by user B. Persistent hash files can also be merged, so that user A can benefit from analysis done separately by users B and C. These various scenarios are the topic of this document."

That looks like very convenient...

I recently came across a fully functional free ramdrive driver, for those interested: http://www.mydigitallife.info/2007/05/2 ... 03-server/

But the Driver is not 64-bit, I saw that also ...

Sorry! I'm still only 32-bits here, so I'm not used to think about this.

I was thinking investing on hardware in the near future. Are there any free 64 bits ramdrive driver? What are the options?

[AdminX]

Everything you might have wanted to know about Rybka III's Persistent Hash.

"In addition, users can share persistent hash files, so that user A can benefit from the analysis done by user B. Persistent hash files can also be merged, so that user A can benefit from analysis done separately by users B and C. These various scenarios are the topic of this document."

That looks like very convenient...

I recently came across a fully functional free ramdrive driver, for those interested: http://www.mydigitallife.info/2007/05/2 ... 03-server/

But the Driver is not 64-bit, I saw that also ...

Sorry! I'm still only 32-bits here, so I'm not used to think about this.

I was thinking investing on hardware in the near future. Are there any free 64 bits ramdrive driver? What are the options?

Here one for you ..., its NOT FREE however.

http://www.superspeed.com/download/trialversions.php

[Marc MP]

Everything you might have wanted to know about Rybka III's Persistent Hash.

"In addition, users can share persistent hash files, so that user A can benefit from the analysis done by user B. Persistent hash files can also be merged, so that user A can benefit from analysis done separately by users B and C. These various scenarios are the topic of this document."

That looks like very convenient...

I recently came across a fully functional free ramdrive driver, for those interested: http://www.mydigitallife.info/2007/05/2 ... 03-server/

But the Driver is not 64-bit, I saw that also ...

Sorry! I'm still only 32-bits here, so I'm not used to think about this.

I was thinking investing on hardware in the near future. Are there any free 64 bits ramdrive driver? What are the options?

Here one for you ..., its NOT FREE however.

http://www.superspeed.com/download/trialversions.php

Thank you. I'll try it when I'll have my new computer.

[bob]

Everything you might have wanted to know about Rybka III's Persistent Hash.

"In addition, users can share persistent hash files, so that user A can benefit from the analysis done by user B. Persistent hash files can also be merged, so that user A can benefit from analysis done separately by users B and C. These various scenarios are the topic of this document."

also:

"1) Set the [Persistent Hash Path] engine parameter to some path on your hard drive where you want the persistent hash file to be placed."

This is why I asked about Ramdisk in my earlier post. My only remaining question is, is there really a 2 GB limit for Persistent Hash? Waiting for Vas to answer ...


Just for the record, this is not a "new feature". Crafty had this ability 10 years ago, the ability to share the "position.lrn" file (an ascii version of position.bin so that a user could combine persistent data from multiple users...

However I am not personally much of a fan of the idea and I even removed the persistent hash completely from version 22.0...


http://www.rybkachess.com/docs/Rybka_3_ ... t_hash.htm

[Tony]

Everything you might have wanted to know about Rybka III's Persistent Hash.

"In addition, users can share persistent hash files, so that user A can benefit from the analysis done by user B. Persistent hash files can also be merged, so that user A can benefit from analysis done separately by users B and C. These various scenarios are the topic of this document."

also:

"1) Set the [Persistent Hash Path] engine parameter to some path on your hard drive where you want the persistent hash file to be placed."

This is why I asked about Ramdisk in my earlier post. My only remaining question is, is there really a 2 GB limit for Persistent Hash? Waiting for Vas to answer ...

Just for the record, this is not a "new feature". Crafty had this ability 10 years ago, the ability to share the "position.lrn" file (an ascii version of position.bin so that a user could combine persistent data from multiple users...

However I am not personally much of a fan of the idea and I even removed the persistent hash completely from version 22.0...


http://www.rybkachess.com/docs/Rybka_3_ ... t_hash.htm

Don't try to confuse the situation with facts Bob.
If Vas takes something existing and improves on it he should be called at least the inventor, if not God.

Tony

[bob]

Everything you might have wanted to know about Rybka III's Persistent Hash.

"In addition, users can share persistent hash files, so that user A can benefit from the analysis done by user B. Persistent hash files can also be merged, so that user A can benefit from analysis done separately by users B and C. These various scenarios are the topic of this document."

also:

"1) Set the [Persistent Hash Path] engine parameter to some path on your hard drive where you want the persistent hash file to be placed."

This is why I asked about Ramdisk in my earlier post. My only remaining question is, is there really a 2 GB limit for Persistent Hash? Waiting for Vas to answer ...

Just for the record, this is not a "new feature". Crafty had this ability 10 years ago, the ability to share the "position.lrn" file (an ascii version of position.bin so that a user could combine persistent data from multiple users...

However I am not personally much of a fan of the idea and I even removed the persistent hash completely from version 22.0...


http://www.rybkachess.com/docs/Rybka_3_ ... t_hash.htm

Don't try to confuse the situation with facts Bob.
If Vas takes something existing and improves on it he should be called at least the inventor, if not God.

Tony

I know. looks to be a world based on hyperbole at times. In my case, we were exporting ascii "book.lrn" and "position.lrn" files that users could share easily and which could be combined if desired. The persistent hash idea is OK for analysis. For games it is worthless. I removed it because it causes more problems when testing because rerunning the same test can lead to false results if you forget to remove the position.bin file first. I forgot to do so enough times that it became more imporant to simplify testing than to try to help learn something about specific positions that is not applied generally in the tree.

[bob]

Everything you might have wanted to know about Rybka III's Persistent Hash.

"In addition, users can share persistent hash files, so that user A can benefit from the analysis done by user B. Persistent hash files can also be merged, so that user A can benefit from analysis done separately by users B and C. These various scenarios are the topic of this document."

That looks like very convenient...

I recently came across a fully functional free ramdrive driver, for those interested: http://www.mydigitallife.info/2007/05/2 ... 03-server/

But the Driver is not 64-bit, I saw that also ...

Sorry! I'm still only 32-bits here, so I'm not used to think about this.

I was thinking investing on hardware in the near future. Are there any free 64 bits ramdrive driver? What are the options?

Here one for you ..., its NOT FREE however.

http://www.superspeed.com/download/trialversions.php

This entire thread makes no sense to me.. Why would one want to use a RAMDRIVE when windows and/or unix has had filesystem cache for years? It makes less sense to copy a big file to a ram drive than it does to let the operating system cache the parts of it being used (all if necessary and enough memory is available). So I guess I am missing the point...