Fedora Team - JMeter Test 3 - PostgresQL - 9 hours

Instance setup and documentation 

1. Fedora 6 Specs

2. Elastic beanstalk (fcrepo-aws-deployer)

   Instance type	OS	Processsor count	Processor Speed	CPU Reservation/Limit	Memory Reservation/Limit	Storage	Java	Fedora	Java configuration options (e.g. -Xmx 2G)	fcrepo commit	Binary Configuration (local, network, S3)
   t3.large	Amazon Linux 2	2			8GB	gp2 ssd	Java 11	6.0.0-beta	Defaults	293d71e251a237f68be337ac94903d154fa355f8	JMeter

3. Database Specs (Using JDBC object store)
   
   1. Postgres
   2. version  12.3.0
   3. RDS db.t2.large
      
      1. processor speed - 8 GB
      2. processor count - 2
4. JMeter client specs:

   1. Local

      OS	Processor Speed	Cores	Memory	Storage (SSD or Hard Disk)	Java	JMeter
      OSX Big Sur	2.3Ghz	4		N/A	8	3.2

   2. Command

      jmeter -Dfedora_4_server=fcrepo-staging.eba-avct3k5v.us-east-1.elasticbeanstalk.com    -Dfedora_4_port=80 -Dfedora_4_context=fcrepo/rest -Dfilesize_min=10000 -Dfilesize_max=100000 -Dbinary_threads=10 -n -t ~/code/fcrepo4-jmeter/fedora.jmx;

JMeter result:

• • Length of run: 9 hours
  • Summary:
  • summary = 1941603 in 08:59:50 =   59.9/s Avg:   152 Min:    99 Max:  3743 Err:     0 (0.00%)

Grafana Detail