Scalability problem

Huh.. I guesse we've passed the limit...

Can you get any more information out on what is causing it specifically?
What happens when you change the multi vocabulary logic?
How many taxonomies and vocabularies do you have?

I would really really like to make geobrowser scalable so any more information would be really useful.

Patrick

Hi,

I have the same problem. I have 20,000 nodes, distributed in a tree structure with one category and several taxomomies. The MySQL query that slows down the proccess is this:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
SELECT
location.latitude AS geobrowser_lat,
location.longitude AS geobrowser_lon,
location.eid AS geobrowser_vid,
node.nid AS geobrowser_nid,
tid0 as term_node_tid,
node.title AS node_revisions_title,
votingapi_vote.value IS NULL AS isnull

FROM location
INNER JOIN node ON node.vid = location.eid
INNER JOIN (SELECT nid, tid as tid0 from term_node WHERE term_node.tid IN (37,38,39,40,41,87,88,89,90,91) GROUP BY nid, tid ) AS geobrowsertemptable ON node.nid = geobrowsertemptable.nid
LEFT JOIN votingapi_vote ON node.nid = votingapi_vote.content_id

WHERE
location.longitude < -8.595771789550781 AND location.longitude > -8.842964172363281 AND location.latitude < 42.272355117933785 AND location.latitude > 42.18642988279498 ORDER BY isnull ASC, votingapi_vote.value ASC LIMIT 0, 30
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I hope the scalability problem can be solved soon.

Regards,
David.