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/.
Harald Welte laforge at gnumonks.orgNik,
On Sat, Mar 03, 2012 at 12:52:25PM +0000, Nik Pakar wrote:
> This tight integration of a db back end will have lot more limitation when
> it comes to scalable deployment. i.e. 100s of BTS connecting to more than
> one BSCs which will need a common database backend as the the HLR.
I have made it _very_ clear that the bottleneck is not the sqlite3
integration. Trust me, the problem is an architectural problem with the
lack of asynchronous processing of subscriber lookups. You are looking
at a symptom, not the cause.
The people involved in OpenBSC have a very good understanding of what
needs to be done. It is a volunteer project driven by poeple who want
to contribute. If you want a scalable database backend, I suggest you
contribute code to first make the subscriber lookups asynchronous, and
then generalize it away from sqlite3.
Regards,
Harald
--
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)