SEARCH CALL:- Large number (>100000) of calls makes search unusable

[s3m1s0n1c]

Hey Team,

I did look in issues for any issues like this one but didn't find any.. So sorry if this issues is already raised..

So I have over 100000 recorded calls in my RDIO instance with a Sqlite3 DB of 22GB

When you go to use the "Search Call" function and select a certain talk group it basically sits there for 5-10-15 minutes and everything else is in rdio is unresponsive until the select query is done.

The Load on the machine seems to rise a little but no where maxing out the CPUs

I'm guessing its a Sqlite3 issue with trying to do a "select from RadioScannerCalls where talkgroup = x" thru 100000 + records..

Is there a better way to construct the sqlitedb with some kinda index to make it faster?

Ive been involved with another project who uses knex as there project is based on NodeJS for better querys
I know rdio is based on GO lang..
Could one use GORM or Squirrel to make the query's a bit quicker for those with larger numbers of calls in there DB?

Cheers Sonic