I am actually thinking of rewriting a few parts of Sider (so it could
benefit from Iocp/proper connection pooling) before v1.0 but havnt
really got the time as it is quite a big task.
But for the problem you mention I *think* I could do it around this
Saturday. Will probably be in a v0.9.1 release.
The day job is very demanding atm. But I have no other plan for Sider
at the moment so I can get this fixed if you want.
Also, if you have a specific use case or perf problem I would love to
hear about it. :)
p.s. if anyone want to try their hands, you can check the
src/Sider/Executors folder for PipelinedExecutor.cs and
TransactedExecutor.cs which gets used when calling .Pipeline and
.Multi respectively.
- chakrit
I'm currently writing about 14,000 keys at once, and i need to to be
done as fast as possible and transacted. I had it pipelined and it was
taking about 2 seconds, i removed it to make it transacted and it
added about 2 seconds. I'd like to cut it down to as quick as possible
so my reads can get the most up to date info. I have another few weeks
before i gotta publish any code so if you can get it done by then, i
might take a look and see if i can figure out how to implement it just
for something to do. Let me know if you get any updates in. Thanks!
But haven't tested this as I don't have access to VS2010 to
compile .NET4 atm. (which was originally used to build everything)
and MonoDevelop isn't quite up to par so absolutely 0 times have I
tested this but theoretically it should work.
Not sure if you're linking with the source or the NuGet package?
If it's the latter maybe I might be able to give you a test version
tomorrow. :/
Anyway, please try it out if you can :)
On Dec 16, 1:09 pm, Chakrit <neuro.pot...@gmail.com> wrote:
> Just did a quick patch before sleep:https://github.com/chakrit/sider/commit/c406e9c439e35ca6ed6aa016f1699...