when i use this module am facing performance issue

Awesome module!

It would be nice if there were an option (maybe there is?) to preload the entire taxonomy into JS so that we don't have to ping the server each time we select a term

bharanikumariyerphp: what you said is too bad English to even begin to understand. But all performance issues have been solved in version 3, so please upgrade to that ;)

KingMoore: No… that would actually be extremely bad. What happens if you have a taxonomy of 10,000 terms? ;) You *can* get client-side caching though! Just go to admin/settings/hierarchical_select and enable the "Cache in a HTML 5 client-side database" setting. Note that this is currently only supported by WebKit! You could write a new cache plugin that uses Google Gears though.

Hi Wim Leers,

Thanks for the reply. I agree it would be bad to have it act that way all the time (dynamically generating a full array of heirarchy terms in javascript on page load), but I think it would be very useful to have that option. Sure it would be bad on vocabs of 10,000 terms, however it would greatly increase performance for heirarchys of a couple hundred terms.

I think it would be a good options is all. It is generally taking me 200-400ms to request each new level of the heirarchy for me, not to mention the overhead on the server running a full bootstrap etc. to serve the terms each time.

I think what bharanikumariyerphp was trying to say was that it was slow loading the new terms when he changes a dropdown.

exactly correct,

what i do, for increase the performance,

I did this,,, that is i EMPTY the cache table from the database,

Then i there any thing i have to do..

Great help

KingMoore: agreed :) HS already has one client-side caching system: a HTML 5 database. This is so far only supported in WebKit (Safari) though. You could write a new cache plugin that simply stores an entire hierarchy in a JS file, and pretend that's a cache. That's not yet written though, so you'll have to write that yourself or sponsor someone, or me, to do it. I created a new issue for it: http://drupal.org/node/284638.

bharanikumariyerphp: Thanks to KingMoore's clarification I now understood what you were trying to say (thanks KingMoore). It sounds like you've got yourself a slow server… KingMoore mentioned load times of 200-400 ms, those are in the expected range. If yours is a lot slower, that means your server is too slow. (Or maybe you've just got a massive taxonomy, in which case you should apply performance tweaks, but I suspect you don't have that.)
Of course, you could also benefit from the aforementioned JS cache plugin (or use the existing HTML 5 database one if you can use WebKit (http://webkit.org/)).

Note to both: you should upgrade to version 3!

Mr. Leers,

Thanks for all the info. I will definately look into writing a caching system that stores the heirarchy in a JS file. Hopefully that is not too difficult to do (doesn't sound it). Unfortunately a Safari only solution doesn't help me much :D. I will also look at v3. I have only just installed and played around with this module for a bout an hour, but at first glance it seems to solve some UI problems we are having.

Automatically closed -- issue fixed for two weeks with no activity.

performance issues is not solved in v3 I have good dedicated server 4xXeonm, 4gb ram and this module still working very slow with 15000+ terms. even drupal's default taxonomy view works much much faster
Very sad that can't use this module...