-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
redis support #1
Comments
+1 for Redis |
Fixed in master. To get it to work you need to adjust
Or, if you want to use TCP:
The only snag at the moment is that you need to delete the :path option if you want to set a host/port combination, because the redis gem seems to give precedence to path. If we changed path to cabinet then the Kyoto-Cabinet option would not interfere. |
Alright, switching to redis should be more convenient now. Simply change mode to :redis and set host or path option. The port is set to the default redis port. Further convenience Dictionary#path returns the active path (file, unix socket or host/port, or 'hash' depending on the current mode). @dshorthouse, let me know if you need anything else. Once we're good to go, we'll release this as 0.1.0. |
Currently, the ML model relies on a feature key-value store that is implemented using kyoto-cabinet or (as a fallback) a regular Ruby hash. Because the feature dictionary is fairly large (probably in excess of 5MB) it is not ideal to use a Ruby hash as this consumes a lot of memory of the Ruby process; the kyoto-cabinet uses a file-based approach which performs very well, however, some users have reported difficulties installing kyoto-cabinet. Redis seems like a good alternative and it should be fairly easy to add as third KV store option.
The text was updated successfully, but these errors were encountered: