commercial support for Redis ?
Aaron Boxer
Does anyone offer commercial support for Redis? We are planning to
roll out a solution using
Redis this summer or fall, and management has expressed concerns about support.
One twist; I am looking at the windows version of Redis.
Thanks,
Aaron
Dušan Majkić
Hi Aaron. I'm glad you are considering using windows Redis.
There are currently two versions of windows redis: Cygwin and native.
Both versions are very close tied to the original specs, and all commands
should work as written on redis.io.
The main difference is lack of fork() on windows platform. I made native
port in a way that BGSAVE internally calls SAVE, which in practice
works, but block (as normal SAVE do)
This affects performance when BGSAVE is auto called on regular
intervals.
Cygwin build uses own fork() which works very differently than
true (unix) one - it copies whole memory from parent to child process.
This limits you to 1,5Gb effective storage (Cygwin is 32bit)
Also there is cygwin.dll dependency and cygwin's license dependency.
That is why I went to port it as native app. It can be found here:
https://github.com/dmajkic/redis
Beside source, latest 32bit and 64bit binaries that pass all tests
are in Download section.
I use this native ported redis via CreateProcess() API with auto saving
turned off. Then I have an full powered beast in mere 200Kb, ready
to support my app. Which is 32bit. And I fire up 64bit redis-server.exe
when started on 64bit windows. That way I use more than 3.7Gb via
32bit app.
Also, Rui Lopes forked my fork, and created support for service manager.
So redis-server can be started as true Windows service. Source is here:
(Note: I haven't tried it, but added code is clean and simple)
While I can't give any commercial support, you are welcome to
use my fork, fork it, and ask for peer-to-peer help, and I'll try to help
as much as my time allows.
Regards.
Dusan Majkic
Jak Sprats
define what you mean by commercial support, and then describe what you
are willing to pay.
most likely someone here has the experience and is a freelancer and
that may satisfy your needs
just a thought, i think a company that specialises in redis support
doesnt exist, but you can tell your company, a single knowledgable
person would suffice as redis is not Oracle, there are not 1000 knobs,
and there is only 20K lines of code, etc....
- Jak
Aaron Boxer
My plan is to use the native port, with no persistence, so lack of fork
won't be an issue. I just need a fast, feature-full in-memory cache.
And thanks for the link to the windows service fork. I will definitely look
into this. Although forks of forks can begin to get dodgy :)
BTW, what type of dev environment do you use to build and debug the native
version. I am an olde c programmer from way back; might want to do some
hacking.
Cheers,
Aaron
2011/1/20 Dušan Majkić <dma...@gmail.com>:
> --
> You received this message because you are subscribed to the Google Groups "Redis DB" group.
> To post to this group, send email to redi...@googlegroups.com.
> To unsubscribe from this group, send email to redis-db+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/redis-db?hl=en.
>
>
Aaron Boxer
My application will be deployed at a hospital, so when the admitting
system is down, the whole place
grinds to a halt. Managers want to have someone to go to that who will
put any Redis issue we encounter
at top priority, to get fixed/worked around asap. Not sure about the pricing.
Now, from reading the newsgroups, I know Salvatore and Pieter are
pretty ruthless about
fixing bugs, so I am not that worried. Although, windows will have issues
of its own, which they will not be as concerned about, I imagine,
since it is a fork.
Cheers,
Aaron
Dušan Majkić
> version. I am an olde c programmer from way back; might want to do some
> hacking.
I use DevKit from RubyInstaller team. It is nice packaged TDM MinGW
gcc 4.5, which works almost flawlessly in compiling ruby gems. I added
Tcl to it - for redis tests. Other than that Console2 and editor. I also
used CodeBlocks IDE when there was need for bug hunt..
I don't use redis as database, I use it for temp app storage, or large cache.
It is started and killed with my app. I didn't test it as long running service.
BTW Redis under hood is small codebase, clean and easy to understand.
That is why it is so popular (or forked and branched so many times).
--
Regards..
Dusan Majkic
Aaron Boxer
Jak Sprats
In windows, the most stable implementation will be running redis in
Debian inside a VMWare Virtual machine.
1.) Cap the Virtual Machine's memory at X. Set redis' max-memory
setting to (X-100MB). {make sure you use redis2.2, it is better on
respecting max-memory}
2.) set up some type of monitoring (there are several packages)
In reality, if a bug happens Salvatore and Pieter will fix it as soon
as anyone possibly could (quicker than Mysql or Oracle) (last time was
22 mins, which I think was a mistake to publicise, because if they
take 30 mins next time, people will be disappointed :).
I think what you need is someone who can handle operations and also
can come up w/ crafty data modelling if somehow something you
programmed starts to explode in size (or implode in performance).
First person that comes to my mind is Josiah, but there are like 4
other people that are qualified on this chain, if you can come up w/
some sort of proposal (person must respond in 60 minutes, they get
paid $X per year) someone may take you up on it, probably just boils
down to if anyone has free time.
The truth is, this mailing list is already what you want (many sharp
people in parallel), and its free, its just not that easy to convince
management because they are worried about emergencies and you do work
at a hospital, so its serious business.
Still, I seem to remember several requests for commercial support,
someone should just step up and get paid :)
- Jak
On Jan 21, 5:34 am, Aaron Boxer <boxe...@gmail.com> wrote:
> Hi Jak,
>
> My application will be deployed at a hospital, so when the admitting
> system is down, the whole place
> grinds to a halt. Managers want to have someone to go to that who will
> put any Redis issue we encounter
> at top priority, to get fixed/worked around asap. Not sure about the pricing.
>
> Now, from reading the newsgroups, I know Salvatore and Pieter are
> pretty ruthless about
> fixing bugs, so I am not that worried. Although, windows will have issues
> of its own, which they will not be as concerned about, I imagine,
> since it is a fork.
>
> Cheers,
> Aaron
>
Aaron Boxer
"due diligence". Also, there preference here is for an actual,
incorporated company
to take on support; since that company would also be assuming some of the risk
involved.
Cheers,
Aaron
2011/1/22 Jak Sprats <jaks...@gmail.com>: