This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

How good is the view filtering these days?

When v6.0 first came out we played with the idea of only allowing users to see the devices that they had some responsibility for. When we tried implementing it though it seemed to cause quite a bit of overhead on the server when refreshing the overview pages and the box became unstable and crashed often.

I am looking into it again and was wondering how others experiences with filtering have gone now that they're up to v6.4. Does it still cause problems?
  • We've never had a problem with view filtering in Orion.
    The trick is to have lots of RAM in the server.
    IIS is very memory intensive, as is the SQL server.

    We run a dual CPU 930Mhz Compaq DL380 with 4Gb RAM.
    It runs a 2.6Gb SQL Database, the Web server, as well as polling 3000 elements.
    When all is loaded and running, there is 1.7Gb of RAM free, so we could get by with "just" 3Gb of RAM and still have some breathing room. The CPU's are a bit underpowered - 1.2Ghz would be better, but it still runs OK as it is.


    -=Cheers=-
    NG