Mac mini Model Performance Comparison
  • I'm curious what kind of performance is being seen with Mac mini's out there. The Mac mini (Late 2012) is their most powerful and customizable model so I'm sure it is the best performing, but I'm curious about the performance quality at higher quantity of cameras with different models of Mac mini.

    For example, I'd be curious to see what model you're using, how many cameras (at what resolution and frame rate), and how you'd personally rate the performance.

    Say you have a current model mini (Late 2014) with 8 cameras at 3MP and 15-20fps (yes, I picked a high FPS on purpose). Is the web interface still snappy for you or does it lag? Do you see CPU overload errors? Can it keep up?

    I've only ever run SS on iMacs and MacBook Pros so I'm curious how the performance rates to those out there using Mac minis. Thank you!
  • It would certainly be interesting to hear users' experience about this. The Mac mini can be an excellent machine for a SecuritySpy server: small and inexpensive, it's the choice for many users. It is a shame however that it is somewhat under-powered, and has actually gone backwards in terms of performance since 2012. I really do hope that Apple upgrades it soon, and includes some fast quad-core models again! This is sorely missed from the current lineup.

    We ourselves have a quad-core 2012 mini for our own internal CCTV system and for testing SecuritySpy, which runs about a dozen cameras at around 10fps each. The mini handles this comfortably with around 75% of the CPU remaining idle at most times. Excellent performance with no lag and responsive web server.

    If anyone one there is looking for a Mac mini to run their SecuritySpy system, I would recommend trying to find a quad-core 2012 model second hand (e.g. on eBay), as these are significantly faster than the current dual-core models.
  • 2012 Mac mini quad i7 2.3 Ghz, 16 GB ram, 512 GB SSD + 1 TB HDD as fusion (plus 4 bay USB 3 external case with 2x2 TB HDDs mirrored dedicated for capture footage).
    6 cameras usually 2x Foscam FI9803 (one P, one EP, both 720p 10fps), 2x Foscam C1 (720p, 10fps), 2x Foscam 8910E (640x480, 10fps) - the 2 FI9803's doing continuous capture plus motion.
    everything responsive - will be upgrading cameras to higher resolution over the next year or so, and likely increasing count to 8 as well.
    Security Spy itself uses 8.5-20% CPU, VTDecoderXPCService using 9-25% CPU
    (at night it's closer to the 8-10% range, daytime with lots of activity/storm increases load of both processes)

    I had originally settled on 10fps a while ago to reduce file sizes - but with newer Security Spy plus mostly H.264 cameras, I can likely increase fps - will do some testing this weekend maybe and post with any changes seen.
    With current 10fps the 720p cameras have 1 hour continuous capture files that vary from 275 MB up to ~760MB - a full day's capture+motion (video+pictures) looks to average 12-13 GB
    I have things set to keep everything for a month and it's only about 500 GB across all 6 cameras.
    My mini also runs Plex media server, MacOS Server, iTunes, BTSync (backup for family computers to mine), iTunes (wifi backups, and playback to airplay speakers) and still is on average 70-80% idle CPU. Chrome across the various tabs & windows I have open uses more CPU time than Security Spy & VTDecoder
  • My Box is 2014 Mac Mini dual-core 2.6GHz, 8GB, 1TB Drive, 4GB USB3 Buffalo Drive Station, 8 Port Gigabit POE Switch TL-SG1008PE and Asus RT-AC68U Merlin router. Cameras are 4-3MP H264 and 2-4MP H264 cameras all running at full resolution, 10 frames a second and set to armed full time with motion activation. Running Remote Patrol for remote access and notifications on a Iphone and Pad.
    Im really happy with this system. Has been stable and I maybe reboot this Mac once a month. The box is dedicated to Security Spy 4 and running in a remote fashion housed with 2 battery backups, Really long HDMI cable and Logitech K400 wireless keyboard. The system is set up for a parking lot with foot traffic and slow moving cars. I set up a friend with a very similar system. He has 7-3MP cameras at full Res and 10 FPS with motion. He is also having the same good experience. It only take moderate intelligence to set up and there is lots of support from Ben and this forum board.
  • I have a 2012 Quad core i7 mini with 16 GB ram 240 SSD. Running version 4.1.1 capturing to an external USB3 drive. I have 12 cameras running 1080p 10 fps 4000 kbs VBR h.264.
    Using less than 30% of the computer's cpu power and ram. I am sure it would go to 16 without a problem, and probably would record as many as 32. The problem would be the older GPU displaying such a high number of cameras. I am holding my breath for a new Mini from Apple this month!
  • I have a Late 2014 Model Dual-core 3.0GHz, 16GB RAM, 960GB SSD. This runs SS and Apple Server. Just running those alone, the machine hardly sweats. (I even make the Mac run FAHControl on full steam, so curing cancer and recording, all at the same time) I have 4, 3M Dahua Cameras on record, and a bunch on View mode only... Hoping Ben changes the License workings, as I need a total of 9... So for now I only record 4 on the mac. I have a Synology NAS (12TB of storage) recording 2 others, and the other cameras ftp images to the NAS. SS records to the NAS, so my whole network is gigbit connections. I have a 24 port netgear switch with 8 POE on a UPS so when power goes out, all the cameras, mac, NAS all keep running.

    This setup is probably more then the typical user would spend... But this is want I knew I wanted, so I slowly worked up to this. Works flawlessly 24/7. Thank you Ben for creating such reliable software! :-)
  • I gotta say, I'm impressed. I just picked up a 2014 Mac mini (2.6GHz, 8GB, 1TB) from a thrift store and I thought something was wrong with how it was reporting CPU usage at first...it's so low! Even though the 2012 mini has the power powerful processor, the 2014 runs my 3x3MP cameras at 20fps and 1x1080 camera at 30fps all without exceeding 16% CPU. As unfortunate as the current Mac mini is from a hardware/upgradability standpoint it seems to do great with SS4. Now, with all of the replies here as well as getting to see it in person I feel much more comfortable recommending the 2014 mini.
  • This is a very interesting thread.
    I run a Mac mini quad core i7 2012 model, 16gb Ram, recording to 4TB USB drive.
    I have on record 4 x 1080p 2MB cameras, and 2 extra 1080P 2MB cameras on view, all running 10fps (reduced from 20fps due to excessive VT usage)

    The Mac runs ok, cpu usage is always around 10%, but VTDecoderXPCservice runs at 40% then slowly increases over 24hrs to 500%+ killing me machine.
    I then have to stop the SS app and start again, and this brings the cpu usage back down.

    I run a home security business, fitting alarms and IP network cameras, so to test and use SS has proven to be a great way to help out customers that want a better motion detection solution. I would like to understand why the VT usage increases over time, but thats a separate issue.
    Like others I would like to add the extra cameras on record, but do not need a licence for 8 cameras, so would like to see some changes in the licensing structure but apart from that I highly recommend a Mac mini with SS4.
  • Repsolkid, I can't confirm that the issue is the same, but I had a latest gen Mac Mini and found that as the temperature increased, performance decreased. So the hotter it got, the more CPU usage from VT and the lower the performance. I eventually switched to an iMac and that solved my problems. Good luck.
  • Mac Mini (mid 2011) 2.5 Ghz Intel Core i5, 8 GB ram, AMD Radeon HD 6630M. I run 4 cameras of varying resolution + this is my local Plex server (1-2 streams at a time). I don't do much recording though, few manual videos here and there as we monitor/train foster dogs. For viewing the 4 feeds this older setup has worked really good:

    http://i.imgur.com/U7Tax6o.png
  • Late 2012 "Server" model, 2.6 GHz i7,16G DDR3-1600, 4 cameras, 75FPS aggregate.

    Motion Triggers Off
    Audio None
    Continuous Capture Off
    Motion Capture Off.

    One IOS app client on http://

    Activity Monitor shows 50-60% of one CPU.
    Doesn't seem to impact normal desktop uses (mail, web), but noticeable impact on other high-CPU apps (Minecraft, etc).

    Oh, and VTEncoderXPCService and VTDecoderXPCService together are using another 40-ish percent, so my total "User" CPU is around 13%, if that helps.

    Going to move SS to a dedicated Mac Mini server, but "not today".
  • Ben,

    Could you consider supporing a hardware survey tool available that can automatically gather hardware information from users that wish to take it? Valve Software (Steam App) sends these surveys out regular.
  • Hi @jms703 we do gather a certain amount of performance information, if the user has enabled the "Send diagnostic information back to developer" option in the Preferences. At the moment we are mainly using this information to analyse errors and fix bugs, however we may embark on further analyses at some point, to see how the different Mac hardware in use by our customers perform under various conditions.
  • I've been running a single HD camera instance of SS on my 2012 Mac mini for several years now with no problems (aside from the latest release!). The run in parallel with Plex and a few other media servers.

    I generally have no issues at all. I do get the occasional slow-down, but it's never caused an issues with recordings or live viewing over the web interface.
  • Mac mini (Late 2014)
    Processor: 1.4Ghz Intel Core i5
    Memory: 4GB 1600 MHz DDR3
    Graphics: Intel HD Graphics 5000 1536MB

    8 Cameras:
    3 @ 6 fps, 5 @ 4 fps
    5 @ 1920x1080, 2 @ 1280x720, 1@640x480
    All @ H.264 format
    Motion capture armed on all 24x7
    CPU for all running normally is approx 40% (based on Camera Info Window)

    The Mac-Mini is also running extensive Indigo Home Automation with Security Spy Plugin

    All run with no issues at all, although if Apple ever bring out a new quad Mac Mini, I would be tempted.

    Both Indigo and SS are rock solid and the support from Ben with the regular version improvements and fast responses really set it apart from other products. Especially like that Ben has released the iOS app to complement the main SW too.
  • Hi @acedout FYI the latest 4.1.3 version fixes all known bugs - use the "Check for Update" option in the File menu in SecuritySpy to update.

    Thanks to everyone posting in this thread, it's very interesting!
  • Agreed, interesting thread. And agreed, the Mac Mini makes a fine SS machine.

    I'm using a headless 2011 Mac Mini (Server), 2.0GHz quad core i7, 16GB. I changed the system disk to an SSD, but that's only because my 5400RPM system disk failed after ~6 years. Motion capture are done to a USB-attached Drobo. I use an HDMI dongle which I find helps performance, and I recommend if you haven't added one. Aside from SecuritySpy the server runs Plex, an iOS caching server, and some lighter server processes.

    I currently have four 2MP cameras and two 3MP cameras, all H.264 @ 8 FPS, motion capture armed on all 24/7. I use non-rectangular motion detection masks, which may or may not matter for CPU usage. SecuritySpy consumes under 15% CPU, and the entire server generally runs under 20% unless Plex is making it work hard. I will likely bump the frame rate at some point.

    @cstout asked about the web interface; I rarely use it as I have iOS devices/apps talking to SecuritySpy (I use SecuritySpy, Spyglass, and Remote Patrol -- no real favorite).

    I heartily endorse SS adding more CPU-consuming features, like person detection, fog & tree avoidance, and alerting me to cob/spider webs on the camera lens. :)
  • Do you have any feel for how the graphics chip in the newer Mac Minis offsets the CPU horsepower requirements of SecuritySpy? I've got a

    Mid-2010 Server with a Core 2 Duo (2 cores, 2 threads)
    that's pretty much overwhelmed with 9 cameras. I could upgrade to one of my 'leftover' machines, either a
    Late-2012 Server 2.6 GHz i7 (4 cores 8 threads) with Intel HD 4000 graphics
    or maybe a
    Late-2014 3GHz i7 (2 cores, 4 threads) with Intel Iris graphics

    Any idea which would be 'better' for SecuritySpy?

    Thanks!
  • Hi @wpns the 2012 machine is going to be the fastest by far, simply due to the fact that it's quad-core. Both the 2012 and 2014 minis should have hardware H.264 acceleration in their GPUs, however this only works for one of the camera's streams - the other eight will be processed by the CPU, and the CPU in the 2012 has the most overall power.
  • @Ben that's very interesting. I didn't know the GPU acceleration was limited to one camera. Is that a limitation of the software or macOS? Is that only true for Intel integrated graphics or is it still true for iMacs/Mac Pro's with dedicated graphics cards?
  • In my brief testing with the 2014 Mac mini I've become a lot more optimistic about using those if there's a budget restriction. Those 2012's have quite the price tag (understandable) right now. I'm hoping to come across a 2011 2.5GHz i5 that I can test as well. From CPU specs it looks very comparable to highly recommended budget PCs that run Blue Iris, for example. SecuritySpy is a superior application but getting a Mac at a low price is always a battle. If I (or anybody else) can start piecing together a more comprehensive model comparison showing max camera quantity, resolution, and FPS then it will be far easier to quote a customer for a system install including SecuritySpy.
  • Hi @cstout unfortunately Apple don't release information about how many hardware H.264 encode/decode instances each Mac can support, as they consider this proprietary information. However I haven't yet come across a Mac (with its default GPU configuration) that supports more than one of each.

    When using multiple similar cameras with H.264 streams you will be able to tell how many are being decoded in hardware by looking at the CPU column in the Camera Info window in SecuritySpy. When sitting idle (all modes disarmed so no recording is taking place), you should see one camera that is using significantly less CPU time than the others - this indicates that it is being processed in hardware. If you see two like this, this would indicate that two camera streams are being processed in hardware.

    As far as I am aware, the Mac Pro (at least with its default video hardware setup) does not support H.264 hardware encode/decode. I'm not sure why Apple chose not to add this capability, it seems like a strange decision.

    It's now been two and a half years since the last Mac mini update - an unusually long time. I really do hope that Apple will stop neglecting these otherwise fantastic machines, and put out some major updates soon including a quad-core model. In the meantime, I would still advise that the 2012 quad-core mini is the best option for SecuritySpy, and you can pick them up on eBay at reasonable prices.
  • Hi all,
    For all customers running SS on Macmini's headlessly (without a monitor):
    As bp33 suggests above, you need to attach an Active (e.g Apple) VGA/DVI/HDMI/DP etc (not Passive PC VGA) adaptor, or HDMI monitor emulator, to restore full (video hardware) performance.
    As covered in this section of SecuritySpys useful F.A.Q, entitled "Can I run SecuritySpy on a headless Mac?" here: https://bensoftware.com/securityspy/helpfaq.php#Headless

    While CPU Speed and CPU cores, can always be held back by a lack of the other, e.g fast Dual core only CPU, or slow Quad-core CPU (i.e you need a balance of both):
    In which case, lower cameras live streaming frame-rate, and/or Resolution (in their own web-interfaces) to compensate.
    While making sure SecuritySpy own Performance is Optimised: https://bensoftware.com/securityspy/manual/#performance
  • Hi Rod, thanks for these links. I have now built my own dongle from a DP-VGA adapter that I had... but is there a place where I can see the improvement ?
    When I look in activity viewer, the vtdecoderservice is still at the same CPU usage before and after I plug in the dongle.
    I am sure the dongle works, as the mac mini switches to vga resolution when plugged in.
  • without a dongle when you screen share the resolution is small, and laggy. With the dongle it has whatever resolution the dongle sets it for, and the UI is more responsive.
    also from the Window menu, there is a "Camera Info" you can select. It shows several things including the CPU usage per camera. As Ben explained it, one of the camera's will be using the hardware decoding from the GPU and will have reduced CPU load, the rest will be using a higher CPU load - possibly the rest will have the same CPU load if the cameras are similar resolutions/frame rates/stream type.
  • Brian, thanks for explaining. Indeed I see those effects you describe.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!