jeremy-cc

path.raw: Descending	Count	50th percentile of backend_processing_time	Max backend_processing_time	1st percentile of backend_processing_time	5th percentile of backend_processing_time	25th percentile of backend_processing_time	50th percentile of backend_processing_time	75th percentile of backend_processing_time	95th percentile of backend_processing_time	99th percentile of backend_processing_time
/crm/authentication/authenticate_api	489	1.396	2.501	1.37	1.375	1.383	1.396	1.488	1.653	1.807
/crm/accounts/account/find	168	19.924	38.463	0.02	0.023	13.953	19.924	22.669	36.868	37.768
/crm/v2/contacts/contact/168997e0-b9

jeremy-cc

Reference: http://www.quickfixj.org/quickfixj/usermanual/1.5.3/usage/configuration.html

Extending market simulator to stub Quickfix

1.  Duplicate functionality from internal/fix_engine/gateway.rb:55, and set up a Fix Engine like structure within market simulator:

    see internal/fix_engine/app/fix/connection/fix_connection.rb:12

2.  Create configuration for the Market Simulator, and configure a FIX session as an ACCEPTOR: http://www.quickfixj.org/quickfixj/usermanual/1.5.3/usage/configuration.html#Acceptor
    An acceptor is a service that listens on a port for incoming connections, and behaves like a server.  FIX Engine itself  is an INITIATOR, i.e. something that connects to a remote server.

jeremy-cc

=begin
  Interface onto sugardirect Contacts
=end
class ContactWebAdaptor < TccWebAdaptor
  register Sinatra::AutodocRoute

  documented_route :parameters => [
      parameter(:rfx_ref, String, 'The rfx_ref of the contact of interest', false),
      parameter(:rfx_refs, Array, 'an Array of rfx_ref values', false),
      parameter(:uuids, Array, 'An Array of uuids corresponding to the primary key', true)],

jeremy-cc

Elasped time | Step definition 
      02m53s | Funds Matcher can import files for failed payment examples 
      01m36s | Plutus payment files: NatWest CSV with multiple payments for a trade 
      01m31s | Plutus payment files: CSV, MT103 
      01m12s | Plutus payment files: NatWest CSV 
      01m03s | Payment files are generated for specified transfer channels and match expected SSI data 
      01m01s | Simple lifecycle of a payment 
      00m58s | Medbank payment file CSV 
      00m58s | Lifecycle of a payment for Medbank via Front-end 
      00m56s | Trade prices are correct in the direct end-client trades, and counter party house trades