4

I'm integrating redis into my NodeJS server app, and I'm trying to figure out whether or not to install node_redis with the hiredis command. I assume that the option to install it wouldn't have been made available if it wasn't useful in some way or another. At the same time, the github page for node_redis (https://github.com/mranney/node_redis) makes it clear that upgrading to newer versions of nodeJS can cause problems with the hiredis option added.

Could somebody lay out the unwritten pros and cons of adding the hiredis vs not? How much of a performance increase is there in going with the C library?

Sergio Tulentsev
  • 226,338
  • 43
  • 373
  • 367
thisissami
  • 15,445
  • 16
  • 47
  • 74

1 Answers1

3

For production I would seriously consider using hiredis parser because it performs better. For testing you do not need it. Then when you deploy new version to the server you just recompile hiredis. That is not such a big deal. Also when you have proper tests in play you would notice when something is wrong with redis/hiredis(or any place else).

Alfred
  • 60,935
  • 33
  • 147
  • 186
  • does rebuilding it effectively mean just running "npm install hiredis redis" again? – thisissami Oct 31 '12 at 20:28
  • does the order matter? the github page makes it sound like hiredis needs to be updated when node is updated, which would lead me to believe that only when node.js is updated do we need to recompile hiredis. – thisissami Nov 01 '12 at 01:03
  • yup then hiredis needs to be updated after installing node.js, but it could also be update using same node.js version (hiredis within node.js version). – Alfred Nov 01 '12 at 06:51
  • What is the current state regarding hiredis and node_redis. The changelogs of node_redis state that the default parser is now faster than hiredis. Do people confirm or deny this based on real-world experience? – Manjabes Nov 28 '16 at 09:00