Hello All,
I used minispy as a base for a file change detecttion driver. This has been
working fine, but now other people were testing it 
One of the tests was to create a dir and a specified number of files with a
specified size.
I detect those creates by checking for the FILE_CREATED in the information
field in the post create operation. Now I am noticing that the bigger the
file size the less of the FILE_CREATED events seem to be picked up. During
Debugging I actually printed out what comes in at “SpyPostOperationCallback”
and I just don’t see some of the create events.
For example I created 30 files with 5KB and I saw 27 creates come in. When I
changed the size to 10KB, I only saw 10.
Now I am wondering where are those other events getting dropped? And why? Is
that a minispy limitation I should be aware of (and that I could fix)?
Thanks a lot for any pointers,
bjorn
“bjorn haake” wrote in message news:xxxxx@ntfsd…
> Hello All,
>
>>
> Now I am wondering where are those other events getting dropped? And why?
> Is that a minispy limitation I should be aware of (and that I could fix)?
Oh, I am realizing that the SPyAllocateBuffer to allocate space for the
RecordList is failing…
bjorn
>> Now I am wondering where are those other events getting dropped? And why?
> Is that a minispy limitation I should be aware of (and that I could fix)?
Oh, I am realizing that the SPyAllocateBuffer to allocate space for the
RecordList is failing…
Well, after further investigation, I still think it’s minispy that cannot
handle too many events coming in. The system testers run a java tests that
creates a bunch of files and appends some arbitrary data (all done in Java).
I was verifying with Minispy that when the first file was created and
written to, there were many writes occurring (something like 5,000).
Eventually the Buffer (allocated with SpyAllocate) reaches its limit (set to
500 in the sample, I changed it to 50,000 with a result slightly improved
but still not working great) and drops subsequent operations.
The question I have: Is this somethign that could be improved/fixed with
replacing the FilterSendmessage with a FilterGetMessage? Or is minispy just
not mant to handle that many operations within a few milliseconds?
Thanks, bjorn