A couple of questions about nsdci

1 view
Skip to first unread message

Jade

unread,
Mar 7, 2007, 6:18:57 PM3/7/07
to nsdci Discussion
Do you have a particular version that is considered stable?

Can this list be added to the commit emails?

Some more information on how this was used at Digital City would be
really valuable. I'm particularly interested in the scalability -- I
imagine it's quite good considering it was for you guys, but can you
give us an idea of what type of scalability to expect?

Did you use elements of this for synchronizing caches?

This looks very exciting -- I'm looking forward to digging deeper into
it.

Nathan Folkman

unread,
Mar 8, 2007, 12:20:33 PM3/8/07
to nsdci-...@googlegroups.com
On 3/7/07, Jade <Jad...@gmail.com> wrote:

Do you have a particular version that is considered stable?

The "head" version is stable.  I'll be rolling out some new tagged binaries in the near future.

Can this list be added to the commit emails?

I went ahead and set up a new Google Group for this:

    http://groups.google.com/group/nsdci-commits

Feel free to join, and you'll be notified of all changes committed to subversion for this project.

Some more information on how this was used at Digital City would be
really valuable. I'm particularly interested in the scalability -- I
imagine it's quite good considering it was for you guys, but can you
give us an idea of what type of scalability to expect?

We're working on some better documentation for this. We need to put together some good bench marks for each of the various components. Perhaps this is something you could help with? That said, this stuff was used across many hundreds of servers.

Did you use elements of this for synchronizing caches?

Yes. NV (network variables), RPC with NCF (network cache-flush), and AV (automatic variables) are all examples of data structures used to update various distributed caches.

If you could describe what you're trying to do, I could try to point you in the right direction.

This looks very exciting -- I'm looking forward to digging deeper into
it.

Thanks! We look forward to getting additional folks involved with the code! :-)

--
Nathan Folkman
nathan....@gmail.com
Reply all
Reply to author
Forward
0 new messages