On Apr 14, 1:45 am, "John Mettraux" <[EMAIL PROTECTED]> wrote:
> This question reminds me of this one 
> :http://groups.google.com/group/openwferu-users/browse_thread/thread/c...
>

The Kisha project looks interesting. It could probably use it for
creating a client/server setup for the engine. However, on my current
production host I can have only one rails application at a time.

> I don't know if you are using ThreadedDbExpressionStorage or its
> parent class DbExpressionStorage. The first one caches expressions in
> memory for quicker reads and queues update requests for snappier
> writes. The second one just does the read / write immediately and
> returns when such an operation is done. The second one
> (DbExpressionStorage) could be OK with multiple mongrels, but it's way
> slower than the first one, I don't know about the kind of business
> processes you are running but this "slowness" might be unacceptable
> for you.

I now use the DbPersistedEngine without caching. The processes advance
slowly (based on human interaction) but with many instances running at
a time. Therefore caching would probably be not very efficient
anyway.

> filesystem instead of the DB. (I'm personally not a fan of db
> persisted expressions, I think it's OK to have workitems stored in the
> db for quick lookup, but expressions storage being rather
> hierarchical, a relational db is overkill, but granted : some admins
> might prefer to have everything in a db).

I choose db storage because of crash recovery (the db server is
shared, clustered, and frequently backed up). But file based storage
should also work fine.

Thanks for your help,

Maarten

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"OpenWFEru users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/openwferu-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to