This commit is contained in:
@@ -18,14 +18,10 @@ Get stress test running, need to be sure
|
||||
maybe the reboot is not the server booting but linux systemctl or dotnet restarting the service
|
||||
|
||||
TODO: Stress test todo:
|
||||
- Parameterize the options,
|
||||
SEEDLEVEL
|
||||
USERCOUNT
|
||||
SERVERADDRESS
|
||||
DURATION_SECONDS
|
||||
|
||||
- Add wider range of random record counts to fetch suitable to large data
|
||||
- Add customer creation with a full set of data if possible generate random notes text (jmeter lorem ipsum)
|
||||
${__RandomString(10,abcdefghijklmnopqrstuvwxyz,)}
|
||||
- Add more types of objects fetched, look for objects not fetched before and add them
|
||||
- Create a memo to a random user
|
||||
- search picklist randomly doesn't have to return results bonus if random list type too
|
||||
@@ -47,7 +43,7 @@ TODO: Get teh amount of space a HUGE seeded database consumes
|
||||
11k customers
|
||||
1814 outside users
|
||||
500 headoffices
|
||||
3k workorders
|
||||
3k workorders (about 11.5 per working day based on 260 working days per year)
|
||||
1k projects
|
||||
200 csr
|
||||
10k parts
|
||||
@@ -59,6 +55,7 @@ TODO: Get teh amount of space a HUGE seeded database consumes
|
||||
200 service rates
|
||||
100 travel rates
|
||||
750 internal users
|
||||
Size on disk = 590mb on test server, so 1gb is about the size of a years worth of data for a small company maybe?
|
||||
|
||||
|
||||
|
||||
@@ -72,6 +69,15 @@ METRIC WE DO NEED
|
||||
just a simple value showing storage space available for subscribers maybe usage over time?
|
||||
but surface outside of OPS tree in menu, in admin? backup?
|
||||
|
||||
|
||||
todo: remove from public view but keep implemented the HUGE database size seeding as it's not really huge at all, more like small data for a years worth of a small company
|
||||
customers are huge but work orders are relatively light, would need to be double I think to come close to huge
|
||||
Instead small, medium, large, huge do tiny, small, medium, large or rename huge to something less huge sounding like largest, or maybe just remove it from the docs and offerings and keep it as an internal test thing??
|
||||
|
||||
|
||||
|
||||
|
||||
.........................
|
||||
reorganize below and then whatever is most urgent
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user