Page tree
Skip to end of metadata
Go to start of metadata

Disk space recommendations

Rationale

FIXEdge constantly generates big volumes of the logs. Long-term work could exhaust all disk space which would result in unstable application operation.

It is recommended to monitor free disk space and set up optimal disk space usage scenarios.

FIXEdge should use a fast storage (e.g. SSD) for session logs to achieve maximum performance.

Under article 25 of MiFIR and RTS 24 MiFID II, operators of trading venues will be required to collect and maintain for at least five years the relevant data relating to all orders in financial instruments which are advertised through their systems. Within the five year period, competent authorities may request these records of orders and transactions maintained by investment firms and trading venues.  

For smart usage of disk space on fast storage, old data could be moved to a different place, e.g. to a network drive. FIXEdge configuration parameters allow configure proper archiving and rotation strategy (see How to configure logging and logs rotation in FIXEdge for more information);

Common recommendations

The following items are to be considered for determining required disk space:

  1. FIXEdge binaries and configuration (~1 GB)
  2. FIX session logs with fix messages.
    Depends on the maximum expected number of messages per day multiplied by the average size of messages;
  3. Application logs (tens - hundreds MB per day):
    1. application status and errors,
    2. sessions statuses changes,
    3. validation errors,
    4. monitoring notes.
    Sessions and messages flow with issues generate more logs than issues-free flow. 
  4. Reserve extra space for core files ( few GB )

Additional items consuming space

Best practice is a reservation space for unexpected consequences.

  1. Database consumes the similar size as sessions logs but it depends on content to be stored.

    It is recommended to have the Database setup on another disk or on different server to make your architecture less vulnerable to failures.

  2. Enabled debug or trace information could generate several times more logging (all above multiplied 3).
  3. Disabled archiving and cleaning up (all above multiplied 365 per year).
  4. Foreseen growth as per business operational plans.
    In fact, MiFID II states that a financial institution should be prepared for handling message twice bigger than the biggest one seen in the previous 6 months (all above multiplied x 2).

Example

For the solution:

  • 130 active sessions
  • 160 000 000 messages pass through the system per day
  • simple routing from one FIX session to another FIX session

Total space:

  • Daily sessions logs takes up 70 GB
  • Application logs occupy 320 MB
  • DB occupy 60 GB

Note

For this example, daily sessions and application logs occupy about 8-10 GB after archiving.

  • No labels