[SERVER-21310] Inject iterations and threadCount into data object in fsm workloads Created: 05/Nov/15  Updated: 18/Nov/15  Resolved: 10/Nov/15

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.2.0-rc3

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-21523 Injected "threadCount" property is de... Closed
related to SERVER-20937 Add mode to FSM framework that drives... Closed
Backwards Compatibility: Fully Compatible
Sprint: TIG C (11/20/15)
Participants:

 Description   

Currently threadCount and iterations aren't available as part of the "this" context for workloads. Thus, workloads that use these as parameters can only access what they're set to initially. When using the load multiplier, any workloads that use the initial versions of these parameters fail because the threadCount has changed from what they expect. If they could just look at data for the updated threadCount, they could pass again.



 Comments   
Comment by Githook User [ 10/Nov/15 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-21310 Inject iterations and threadCount into data object in fsm workloads
Branch: master
https://github.com/mongodb/mongo/commit/904c99891b47935ff7c0856f4456303f32c04f11

Comment by Kamran K. [ 05/Nov/15 ]

Sounds good to me.

Comment by Max Hirschhorn [ 05/Nov/15 ]

Could we do that and also define a setter for the property that throws an error?

Comment by Kamran K. [ 05/Nov/15 ]

I was thinking we could just define non-enumerable, non-configurable, non-writable properties to avoid namespacing. One drawback is that assignments will silently fail.

Comment by Max Hirschhorn [ 05/Nov/15 ]

What's the plan for "namespacing" the iterations and threadCount properties to distinguish them from properties that the workload may set while it is running?

Generated at Thu Feb 08 03:56:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.