Not logged inRybka Chess Community Forum
Up Topic Rybka Support & Discussion / Aquarium / Connection of network engines to tables
- - By Viktor (**) [ru] Date 2017-10-13 07:20
Don't work endgame table network engines. In the Central computer in the network engines point the way to the tables. But this is not enough. So, probably, it is necessary to register by opening RTSingleServer.ini. But how to do it correctly?
The engines that work from the CPU, work.
Parent - By OempaS (***) Date 2017-10-15 21:31 Edited 2017-10-15 21:33
Put the tables on the remote computer.
On the central computer you must set each engine to point to the tables on the remote computer.

No action needed in the rthomeserver.ini file
- - By Viktor (**) [ru] Date 2017-10-16 16:42
How can I specify the path to Tables on the remote computer, if the settings are the engines on a Central computer?
If the Internet is weak, then the response will be poor. Yes, and SSD is not there.
Parent - By pawnslinger (***) [us] Date 2017-10-17 00:27
I have never tried using Aquarium in a networked environment... so perhaps I don't know the answer.

Having said that, it seems that endgame tablebases must be: (1) local to the engine using it, and (2) on the fastest media available (of course, SSD preferred).  Otherwise, the best choice would be to skip the use of endgame tablebases.  As it seems to me that raw engine power would be faster than waiting for slow media (or network connection).

On some of my endgames, the tablebase hit count is in the millions... any idea how long that would take across a network?  Compared to my local SSD?  It would spend a lot of time waiting for the tablebase hits to come back, I believe.
Parent - By OempaS (***) Date 2017-10-17 05:29
For the local engines put the tables on the local PC. And point the local engines to these local tables.
For the remote engines put the tables on the same remote PC as where you put the remote engines.
On the local PC in the settings of the local engines point to the tables on the local PC.
On the local PC in the settings of the remote engines point to the tables on the remote PC.
Best to use SSD for the tables but not really necessary.
- - By Viktor (**) [ru] Date 2017-10-17 13:01
I have connected via the Internet connection since I can't specify a path through the network on another computer.
Parent - - By Ghengis-Kann (***) [us] Date 2017-10-17 17:28
Hello Victor.

If you are using a Windows-based system then it is best to make all of the computers part of a "Home Group" and then share the relevant folders with the entire group.
I do this and share out the root drives so that I have access to everything on all of the computers from any one of them, but if you are in an environment where data security is an issue then you might want to share out only the necessary folders.

Once everything is on the home group you will have the ability to type or copy and paste a path to something on another computer.

I do this with a wireless router, and have found that it is best to fix the internal IP addresses so that they can not change.
The router assigns subnet addresses in a seemingly random fashion, which can cause the address to change if there is a power failure that affects the router.
If you specify the address in the router configuration software it will not change.
Parent - - By cma6 (****) Date 2017-10-21 03:13
"I do this with a wireless router, and have found that it is best to fix the internal IP addresses so that they can not change.
The router assigns subnet addresses in a seemingly random fashion, which can cause the address to change if there is a power failure that affects the router.
If you specify the address in the router configuration software it will not change."

Ghengis:
  My LAN has 4 wired slave systems connected to a master system. My Netgear router software displays the IP address and Windows name for each of the 5 systems. But I don't see any way to require the router to maintain those IP addresses after a power failure affecting the router.
Parent - - By dickie (**) [gb] Date 2017-10-21 06:27
Use the computer name rather than the IP address to link your network computers. Then you do not have to worry about your router changing IP addresses.
Parent - By cma6 (****) Date 2017-10-21 17:30
Great idea!
Parent - - By Ghengis-Kann (***) [us] Date 2017-10-23 19:17
A Netgear router should have a self-assigned IP address of either 192.168.0.1 or 192.168.1.1.

Type that into the address bar of your browser.
It will bring up a login screen where the default credentials are admin and password.

Somewhere in the menus you will find a place to assign static IP addresses that pair a Media Access Control code to a subnet address that will be something like 192.168.0.xx, where xx specifies the address of that computer within your LAN. The MAC codes of the individual computers can be found in various ways, but I just go to a command prompt, type ipconfig/all, and look for the hexadecimal code that is listed as the physical address.

Dickie's idea of using the computer name to link the computers is exactly what the Windows home group does, but the computer name is just a label for the MAC Code.
My experience has been that a power failure that affects the router can cause different IP addresses to be associated with those same computer names, which severs the connection of Aquarium to the remote engines. After the second time I had to set up 40 remote engines in IDEA because of this I figured out a way to stop it from happening.
Parent - By cma6 (****) Date 2017-10-23 23:56
Thanks, Ghengis, your methods looks to be even more safer--but harder to implement--than Dickie's method. So I will do the easiest one first :)
Up Topic Rybka Support & Discussion / Aquarium / Connection of network engines to tables

Powered by mwForum 2.27.4 © 1999-2012 Markus Wichitill