--
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.
There is nothing 32bit specific, except the fact that I work on 32bit windows.
I simply had no way to run tests on 64bit exe.
64 bit builds will arrive as soon as I get my hands on it.
Also, nothing stops you to try to build it yourself.
I'll install Win64 VM on laptop.
Give me some time to get into how MinGW-x64 works.
Regards.
Cheers,
Salvatore
> --
> 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.
>
>
--
Salvatore 'antirez' Sanfilippo
http://invece.org
"We are what we repeatedly do. Excellence, therefore, is not an act,
but a habit." -- Aristotele
It will not be that easy to port it. There are enough types that
are different size in Unix and in Windows, that this port will
become a full fork of Redis project.
And there was a series of recent commits that changed a
lot in code base: client went hiredis, cluster is comming,
unix socekts are supperted, etc...
Mester rep is brewing and buzzing. This is a good thing,
but I have ony spare time to track it and work on it.
On the plus side, I have it compiling and I'mworking on
tests that fail.
Yes. There are a number of places where there is something like:
long x = (long) o->ptr;
Ok for 32bits, but 64bit does different in Windows than on Linux.
Long longs are used whenever possible, but sitll,
every (long)something is potential error on windows.
Then there are 64bit file access issues (32bit offsets) and like,
since msvcrt is used. These should be tackled with MinGW
replacements and if that doesn't fit, with WinAPI.
Timings are also different: nt ticks on 10-15ms, so
high resolution timer should be used. Etc..
> Do you think it is even in the long run a 'mission impossible' to have
> a production ready win64 version of redis that keeps (nearly) up to
> date with the official releases?
There is a great usage niche for win64 redis. It can provide access
to full 64bit memory from 32bit app, with very little overhead.
Simpler than shared memory, and faster than file based dbs.
Now, I know that Salvatore and others took the "redis-on-server"
road, but I find this "redis-on-client" very interesting. If it can be
done, and done right, I'll be the first one to use it.
> Do you need some help with this?
I'll push 64bit buildable source to github as soon as it builds
something stable. Feel free to do do what ever you like with it
and, of course, any help appreciated.