Thanks for the response - no it hadn't occurred to me to try a different
network filesystem, as I don't really have access to non windows machines.
I'm just using windows xp machines set up on the same domain, where the
databases reside on shared folders.
I actually thought there might be extra work sqlite is doing (no not
sleeping!) when more than one client is accessing the same database, like
having to move between extra locking states or something like that, and that
it might be easily explainable, but you're perfectly right that it could
just be down to the OS.
thanks anyway,
Serena
On Tue, May 20, 2008 at 9:34 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
>
> That is probably a question that cannot be answered without knowing
> specifics of your network filesystem. Certainly we have NOT put code
> in SQLite that says:
>
>
> if( serena_is_accessing_multiple_times_on_network_filesystem()==TRUE ){
> sqlite3_usleep(6000000);
> }
>
> I really do not know why it goes slowly on a network filesystem when
> two or more clients are connected. I would guess it has something to
> do with the locking and caching protocols of your network filesystem.
> But that is only a guess. You talk as if this behavior is true of
> every network filesystem. Is that true? Have you tried on a
> different network filesystem? If you really need to know why it is
> slow, open the code, attach a protocol analyzer to your network, and
> figure it out. Let us know if you find anything interesting.
>
>
> D. Richard Hipp
> [EMAIL PROTECTED]
>
>
>
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
