| Java menu knowledge base
Support - Scalability
"I’m evaluating your product and I must congratulate you on an excellent job. I’ve tried no less than 15 [different menu products] and you are the only ones that are really capable of managing hundreds and thousands of items in a reasonable amount of time. ...I've tested eNavigator, iNavigate, SiteXpert and many others." Esteban Castro, Managing Director, Metanoia Ltda. (January 2002)
Where can I find scalable menu solutions?
Most client-side menu solutions (both DHTML and java) will crack up after just a very few hundred menu items at best. Servers can handle much largers menus, but they cannot deliver the content to the client fast enough and run into performance problems. A good menu system needs high client-side scalability and performance.
For many years, IMINT.COM has been the only company with the technology to provide truly scalable client-side navigation solutions. This
means that not only is our technology state-of-the-art, so is our experience in advising
on scalable solutions and strategies.
How can I believe you?
Read our money-back scalability guarantee. Or
download a fully-featured trial version and prove it to yourself before
you spend anything. Or look at our online demonstrations with indices of
between 1000 and 5000 items - none of our competitors show you anything even approaching this.
How scalable are you?
(1) We believe that, properly implemented and exploiting to the full our various scalability strategies, our top menus can smoothly handle the client-side interface to 1,000,000-item databases and greater. (2) Even using our most basic settings and with no special strategies, 5000 items or so (on the client) is easy. (3) We
have tested one of our top menus successfully with 100,000 menu items loaded client-side at the same time.
So why does my IMINT.COM menu stop after 50, 100 or 1000 items?
- If it stops at 50 or 100, this is probably because you are
using one of our little free or "mini" applets. Solution: download
a fully-featured trial of a Pro or Pro-X applet here.
- If it stops at 1000, this is probably because you have not
found the indexmaxsize parameter. Solution: set this
parameter to something higher than 1000.
Are the trial versions equal in scalability to the release versions?
Yes. (But check the version numbers - sometimes trials will be a slightly
older version than the latest release).
I need vast scalability. What strategies should I look at?
If you're using 1000 items or so, you don't need any special strategies (but you should
nevertheless compress your indices).
If you're heading much higher than this, then start thinking about:
- Compressed content delivery (increases loading speed by about 900%)
- Path-substitutions (increases loading speed by about 25 - 50%)
- Streaming indices (unlimited capacity extensions)
- Use of your own server-side scripts for interfacing efficient menu content
delivery with your database: read this, this, this, this, this and this.
- Custom solutions drawing on IMINT-COM's scalability experience
|
|
