hmm, concerning
On Tuesday, June 2, 2015 at 4:33:25 PM UTC+2, André Marques wrote:
>
> I did some load tests using the connection pool and had some problems, I
> don't think the connections are threadsafe, or is not stable.
> Using one connection for all requests didn't work well, looks like the
> connection executes only one statement at time.
> Then I tested using one connection per request and the response time were
> a lot better.
> I think that the connection per request is the best way right now.
> I'm new to orientdb, so I might be wrong.
>
> To close the connection you have to call the close() method
> var server = oriento({...});
> var db = server.use({...});
> ...
> server.close();
>
>
>
>
> On Tuesday, June 2, 2015 at 6:51:32 AM UTC-3, Samuel Goldenbaum wrote:
>>
>> thanks Andre
>>
>> From what I undertand Oriento will open a new connection as needed when
>> you try to access the db - at what point is this connection closed? Are the
>> connections threadsafe?
>>
>> On Monday, June 1, 2015 at 4:38:55 PM UTC+2, André Marques wrote:
>>>
>>> Hi,
>>>
>>> You can also use the connection pool:
>>>
>>> var server = Oriento({
>>> host: 'localhost',
>>> port: 2424,
>>> username: 'root',
>>> password: 'yourpassword',
>>> pool: {
>>> max: 10
>>> }
>>> });
>>>
>>>
>>> On Friday, May 29, 2015 at 4:12:27 AM UTC-3, Samuel Goldenbaum wrote:
>>>>
>>>> What is the recommended way to manage OrientDB connections in
>>>> Express.js or any web application for that matter? Connection per request?
>>>> Would be using the oriento Node.js driver.
>>>>
>>>>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
