Re-evaluate Ingest & Fetch perfo test

[Yalz]

Current JMeter test case for both Ingest & Fetch looks as follows. This due to the requirement of having to both ingest and fetch at the same time.

However, this slows down the perfo test itself and feels quite unnatural. To revise

sequenceDiagram
    critical Init of Server
        JMeter->>Server: Create collection
        JMeter->>Server: Create geospatial view
        JMeter->>Server: Create timebased view
    end
    par Ingest of members
        loop For each member in 10k member data source 
            JMeter->> Server: Ingest member
            JMeter->>+ Mongo: Request and wait for allocated member fragment
            Mongo-->>-JMeter: 
            JMeter->>+ Server: Request member fragment 
            Server-->>-JMeter: 
        end
    and Fragmentation Processing
        JMeter->>+ Mongo: Verify if geospatial view contains 10k members
        Mongo-->>-JMeter: 
        JMeter->>+ Mongo: Verify if timebased view contains 10k members
        Mongo-->>-JMeter: 
        opt Fragmentations have finished
            JMeter->> Report: Write final report
        end
    end

[Yalz]

Will be picked up as part of load testing effort

[jobulcke]

Closing since is no longer relevant