I have put together a list of capabilities that I will need to generate tag
reader load against our Data Cpature/Premises infrastructure.
I am not sure if these capapbilites are currently avaialble within rifidi but
it was not obvious from the XML tags that were in the sample XML files. (see
point 5)
1. Wait times between events within a segment should have some variablity,
instead of a single wait time. We need to support a range of wait times that
are chosen randomly, such as 5000-15000 (mSec) instead of just a single value.
This prevents events from multiple readers from becoming synchronized at
certain times and causing artificial spikes in load.
2. We need to specify the number of times a test is run; need more grainularity
than once or forever, unless there are looping constructs available within the
XML file that would let us iterate a pattern of tag reads for a fixed number of
times.
2a Need a looping or iteration construct that would allow if to apply a
pattern of tag reads for a number of iterations.
3. As we discussed previously, our current environment needs to be able to
create a prefix for tags that we generate. We are currently using 96 bit tags
(24 hex chars), the first 16 bits of which (4 hex chars) have a specific
prefix. We use this to define 2 different types of tags based on the prefix.
The rest of the tag id (the remaining 80 bits) need to be unique for the
duration of the run.
4 In the segment definition there is a place to specify tag adds and tag
removes as well as a duration. Does this duration occur before or after the tag
adds and removes or is it the duration of the segment which includes the time
it takes to add or remove the tag? I need more specifics on how this duration
is deterimined.
5. Need some documention for what XML tags are allowed, a simple schema would
be helpful to know what options are available in the existing tag streamer XML
file
6. Control of GPI lines from within the XML file to toggle specific line high
to low, or low to high.
(we have discussed this already)
7. The current XML tag streamer file has reader definitions contained within
the segment definitions. While this is fine for simulating a fixed assembly
line of tags passing by one or several readers it is not sufficient for a
general load generation scenario where readers can be geographically dispersed
and not exposed to the same set of tags.
Is it possible to specify a pattern of tags (and GPIO events) on a per
reader basis so that each reader can generate tag reads and interact with the
gateway/data capture independantly?
I think that meeting these requirements are necessary for most general purpose
tag streaming applications, especially when it is being done to drive
significant loads for system test or performance measurement purposes.
Regards,
Scott
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Rifidi-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rifidi-developers
