Change Details

Currently, wdqs-categories is running on baremetal machines with 128 GB RAM, 32 or more cores, and RAID-0 backed SSDs. Before we move them to a separate environment (VMs or Kubernetes), we need to make sure the new environment has enough power to accommodate wdqs-categories. Creating this ticket to: - Measure current usage in terms of HTTP interactions (hits per day, requests per second etc) - Devise a test that roughly approximates this level of usage - Report the results

Currently, wdqs-categories is running on baremetal machines with 128 GB RAM, 32 or more cores, and RAID-0 backed SSDs. Before we move them to a separate environment (VMs or Kubernetes), we need to make sure the new environment has enough power to accommodate wdqs-categories. Creating this ticket to: - Measure current usage in terms of HTTP interactions (hits per day, requests per second etc) - Devise a test that roughly approximates this level of usage (note that internal and external endpoints might not get the same level of traffic, so both should be tested) - Report the results

Currently, wdqs-categories is running on baremetal machines with 128 GB RAM, 32 or more cores, and RAID-0 backed SSDs. Before we move them to a separate environment (VMs or Kubernetes), we need to make sure the new environment has enough power to accommodate wdqs-categories. Creating this ticket to: - Measure current usage in terms of HTTP interactions (hits per day, requests per second etc) - Devise a test that roughly approximates this level of usage (note that internal and external endpoints might not get the same level of traffic, so both should be tested) - Report the results