Avoid LCR-Stalling

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Holger Hans Peter Freyther holger at freyther.de
Tue Aug 10 14:44:44 UTC 2010


On 08/10/2010 09:56 PM, Konrad Meier wrote:
> Dear List,

Hi Konrad,


> But this can only be considered as a quick hack because in case of a system
> failure all changes to the database are lost.
> 
> Is someone at the moment working on a interface to a better database system?
> Maybe I find some student who can do this.

do you have an idea why it is stalling? Is the executed query so complex or is
someone trying to write into the database while we try to find a subscriber?
At the 26C3 (IIRC) we had issues with blocking the database as we
had a separate process that locked the database for its queries.

It would be very nice if you could find students as we have plenty DB related
tasks where we could need a hand. Some of these could include:

	-) Figure out why we are stalling (rw locks inside sqlite?)
	-) Create an index for the sqlite databases... (proof it is making
           things faster with a standalone benchmark having the same pattern
           as bsc_hack in your network...)
	-) Making the DB interface asynchronous (send and forget, send and
           async reply)
	-) Maybe go so far to use TCAP/MAP and implement a proper VLR module..





More information about the OpenBSC mailing list