Vess Promise Servers




  • Official comment
    Tony Luce

    Hey Harry - 

    Couple things:

    1. You don't need a Xeon CPU to run Nx Witness. A Core i3 is enough to handle 128 streams (actually just a single core of a Core i3 is enough). So you can use very cost-effective hardware when building systems. One of the key features of the Nx is its ability to run amazingly and stably on off-the-shelf hardware. So if you're looking to create a competitive solution feel free to look around. Here are our minimum server hardware requirements for your perusal.

    2. We always suggest our customers take advantage of our Server Hive architecture to create more redundancy in a system. Failover is free - and the Client playback (live and recorded) is seamless no matter where the video being played is stored. So if you're looking to do 128 cameras, for example, splitting this over 2 servers is a great idea. Or maybe even 4. 

    That being said - we work with Promise as well - so any of their solutions are going to be good to go.

    Comment actions Permalink
  • Avatar
    Envy Admin

    Hi Tony,

    Thanks for the prompt reply, just some follow up:

    What kind of cameras/codec is that taking into account? The system we are installing is using ~120x 8MP cameras using H.265. Promise specified the system as requiring 4x A3340s, stating that the H.265 requires significantly higher processing power... This does seem extremely excessive but just want to get your view on it?

    - Assuming 4x Nx Wall Clients with 2x screens each running 4x cameras

    - Our current solution is to use 2x custom built servers, using E3-1230v6 processor +16GB RAM based on the supermicro x11SSH platform in their 2U 8 Bay chassis


    Comment actions Permalink
  • Avatar
    Tony Luce

    Harry - I'm sorry. Somehow I missed this.

    128 Streams on a single core has a reference point of 1080p, 30 fps.

    I would separate server machines from Clients as Clients will be more intensive. We say 4 HD streams per CPU core on a client. 

    H.265 does require more processing on the Client side. Given the level of H.265 that is out there (not much) I can't give you a good answer here, so maybe better safe than sorry on an initial install.

    On the Server side we're simply acting more like a traffic manager, so I'm guessing H.265 won't have much an impact on Server requirements.

    Comment actions Permalink

Please sign in to leave a comment.