Is this similar to geode/gem fire?
I'm not aware of these so I can't say
GhostDB – A Fast Distributed Cache
31–37 of 37 posts
Re: GhostDB – A Fast Distributed Cache
#32Doesn't Redis already address all of this?
Yes, probably with superior performance. The clustering model seems to differ, but as far as I can tell, the 'distributed' part of this project isn't really implemented.
Depending on the use case. If this is being used to reduce load on your database, then there are no noticeable differences between performance of GhostDB or redis from the clients end.
Re: GhostDB – A Fast Distributed Cache
#33Doesn't Redis already address all of this?
Same question. How is this different from Redis?
Not too different from Redis at the moment, however this is straight out of a university project were we had a tight deadline and had to limit scope considerably but if you check the roadmap on the repo we want to add a lot to it.
Re: GhostDB – A Fast Distributed Cache
#34> in-memory, general purpose key-value caching > GhostDB can provide you with up to a 25x increase in data retrieval speeds when compared to databases such as MongoDB and MySQL. Isn't it insincere to say your tech is faster than a DBMS which works on a slower hardware.
Not associated with the OP, but I don't think so. It really does return your data 25x faster than a disk-based DBMS. The implied reduction in durability from being in-memory is clearly stated up front.
Given that you can configure any DB to use extra RAM as a cache, and many datasets will fit in that cache, if I was a fact checker I'd give the "25x faster" rating at least a "partly false" rating.
Re: GhostDB – A Fast Distributed Cache
#35> in-memory, general purpose key-value caching > GhostDB can provide you with up to a 25x increase in data retrieval speeds when compared to databases such as MongoDB and MySQL. Isn't it insincere to say your tech is faster than a DBMS which works on a slower hardware.
Not associated with the OP, but I don't think so. It really does return your data 25x faster than a disk-based DBMS. The implied reduction in durability from being in-memory is clearly stated up front.
Yeah but it is not something that is cultivated from your effort.
Re: GhostDB – A Fast Distributed Cache
#36Earlier quoted context omitted.
Yeah, I've seen people do that but I've glanced the code, it's certainly not the case here.
We're aware of the issues this could cause and we will be looking into relieving GC pressure
Great. Good luck. As someone who's worked on the redis codebase, I suggest you take a good look at some of the design decisions and optimizations that project took, e.g. wrt persistence and replication.
Re: GhostDB – A Fast Distributed Cache
#37for nojs folk: http://archive.is/U8tTA
OP: fyi, your site fails to load or display anything besides a "loading" spinner which never goes away if js is disabled in browser.