| Anonymous | Login | Signup for a new account | 2013-06-19 17:50 CEST | ![]() |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
| 0001618 | SUMo | Refactoring | public | 2012-07-01 21:24 | 2013-01-05 14:43 | ||||||||
| Reporter | bytehead | ||||||||||||
| Assigned To | Kyle_Katarn | ||||||||||||
| Priority | low | Severity | minor | Reproducibility | N/A | ||||||||
| Status | acknowledged | Resolution | open | ||||||||||
| Platform | OS | OS Version | |||||||||||
| Product Version | |||||||||||||
| Target Version | Fixed in Version | ||||||||||||
| Summary | 0001618: Batch mode checking protocol instead of the serial one | ||||||||||||
| Description | Currently SUMo checks every detected item one by one, which is theoretically suboptimal in terms of possible spikes of server load created and subsequent increase of probability of timeouts/DoS situations. Also, this checking mode creates some extra traffic overhead. I think it would be beneficial to implement a batch checking mode instead. This could improve overall stability and performance of SUMo solution. Besides, due to much larger information chunks of requests/replies in the new protocol it could be possible to also take advantage of some compression techniques (like http 1.1 gzip, or similar) and save on the server support costs a bit. | ||||||||||||
| Tags | check | ||||||||||||
| Attached Files | |||||||||||||
Relationships |
||||||
|
||||||
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2012-07-01 21:24 | bytehead | New Issue | |
| 2012-07-01 21:25 | bytehead | Tag Attached: check | |
| 2012-07-01 21:32 | Kyle_Katarn | Assigned To | => Kyle_Katarn |
| 2012-07-01 21:32 | Kyle_Katarn | Status | new => acknowledged |
| 2013-01-05 14:43 | Kyle_Katarn | Relationship added | related to 0001889 |
| MantisBT 1.2.15 [^] Copyright © 2000 - 2013 MantisBT Team |