I think pre-event buffer in mocord mode is a non-sense, because in you are recording all the frames.
If bulk frame would work correctly, you can browse all the frames starting from the alarmed frame going "Prev" and "Next".
Even if all the images are into the filesystem, at this moment, you can start "event investigation", displaying the alarmed image and you can view "Prev" image only if you are under frame#100.
You can view the "Next" images until you arrive at the next bulk frame.
This did not happened in version 1.29 where you can view all the frames.
@marcmerlin, if you do not have high load, and you are experiencing frame loss, in particular way when an alarm occurs, I solved the problem adding the following lines into my.cnf:
Code: Select all
[mysqld]
innodb_read_io_threads=4
innodb_write_io_threads=8 #To stress the double write buffer
innodb_buffer_pool_size=2G
innodb_buffer_pool_load_at_startup=ON
innodb_log_file_size = 32M #Small log files, more page flush
innodb_log_files_in_group=2
innodb_file_per_table=1
innodb_log_buffer_size=8M
innodb_flush_method=O_DIRECT
innodb_flush_log_at_trx_commit=0
skip-innodb_doublewrite
Give it a try! I had frame loss issue with only 2 cams and very low load!
I am using 5 ipcam 1280x720 at 25fps and one 1280x960 at 20fps, all in mocord mode and I get no frame loss. I set up event length at 10min, so I have total 14985-15000 frames for each 720p camera at 25fps, and 11980-12000 frames for the 960p @20fps.
Server is Xeon e3-1246V3, and ZM runs into a Esxi 6.5 virtual machine. Virtual machine load does not go over 1.6-2.0!
Hope it can solve part of your problem.