Bug #238
Timestamp inconsistency
| Status: | Assigned | Start: | 21/01/2010 | ||
|---|---|---|---|---|---|
| Priority: | High | Due date: | |||
| Assigned to: | Jolyon White | % Done: | 50% |
||
| Category: | client+server | ||||
| Target version: | 2.5.0 |
Description
There seems to be a problem with the oml client timestamps. Indeed, running an experiment, we found that at some point if we stress test the server, the oml_ts_client field contains some gaps of several seconds, and then in less than one millisecond almost 50 measurements are performed.
History
Updated by Jolyon White 5 months ago
Guillaume, this might be fixed now that the oml2-server uses SQL transactions. Could I ask you to re-run your test to see if it still causes these gaps in the timestamps? The transactions code is in the master branch, but not in release/2.3.
Updated by Guillaume Jourjon 4 months ago
- File AverageWindowThroughput.png added
With the new use of SQL transactions it seems that this bug disappears but we need more testing on the subject.
I put as attachment the result graph of TCP on a LAN 100Mbits. Basically in this case we are injecting in the database 2 measurement per packet of data + 2 measurements per ack.
p=.!AverageWindowThroughput.png!
Updated by Guillaume Jourjon 4 months ago
- % Done changed from 0 to 50
Updated by Jolyon White 11 days ago
- Category set to client+server
- Status changed from New to Assigned
- Assigned to set to Jolyon White
- Priority changed from Normal to High
- Target version set to 2.5.0