[OpenSER-Devel] RFC: memory management in database modules
Bogdan-Andrei Iancu
bogdan at voice-system.ro
Fri Feb 8 11:13:05 UTC 2008
Hi Victor,
Yes, I know your patch and I plan to use it as start point (patch id
1717848).I will port it to 1.4 and then add the DB API support and
extend usrloc/auth_db to make use of it.
Thanks and regards,
Bogdan
Victor Gamov wrote:
> Hi Bogdan!
>
> Sometimes ago I make patch for 1.2.0 which introduce prepared statements
> into mysql module. This patch was removed later because it incompatible
> with current versions of OpenSER but I still have in mind to reproduce
> this patch for CURRENT when DB API will be stable.
>
> So if you plan to add support for prepared statements you can see into
> this patch (It was worked for our 1.2.0 installation for some time but
> now we use 1.2.2).
>
> This patch changes driver only not other modules like usrloc or other.
> But introducing new DB API function allowing prepare statement and then
> use it in module may be more effectively.
>
> Bogdan-Andrei Iancu wrote:
>
>> Hi Henning,
>>
>> I'm really interested in focusing on things that really drawback openser
>> (as throughput) - and I do not refer at the non-sense lab tests (TM
>> performances :P) which more or less have 0 relevance in real life scenarios.
>>
>> So, as a first plan, I wan to do some work on the DB part : I want to
>> add support for prepared statements which will give some speed up in
>> standard DB queries - 90% of the queries are standard and there is no
>> need to prepare, build query, pass it to the driver, to parse it (by
>> driver), etc.... I want first to add this support in usrloc module, only
>> for mysql backend.
>>
>> If the result are promising, we can extend this to all modules using DB.
>> Then, we can investigate which other drivers support prepared statements
>> and to enhance them also - if not native supported, we can do it the
>> openser module.
>>
>>
>> I know this is a long shot, but first I want to experiment with usrloc
>> and mysql to see if really makes a difference.
>>
>
>
>
More information about the Devel
mailing list