2012 Torneo Internacional AGT – Doubles
Rajeev Ram and Bobby Reynolds were the defending champions but Reynolds decided not to participate.
Ram played alongside Travis Parrott, losing in the semifinals.
John Peers and John-Patrick Smith won the title, defeating César Ramírez and Bruno Rodríguez 6–3, 6–3 in the final.
Doubles | |
---|---|
2012 Torneo Internacional AGT | |
Champions | |
Runners-up | |
Final score | 6–3, 6–3 |
Seeds
Travis Parrott / Rajeev Ram (Semifinals) Andre Begemann / Jordan Kerr (Quarterfinals) Pierre-Hugues Herbert / Albano Olivetti (Semifinals) Colin Ebelthite / Simon Stadler (Quarterfinals)
Draw
Key
- Q = Qualifier
- WC = Wild Card
- LL = Lucky Loser
- Alt = Alternate
- SE = Special Exempt
- PR = Protected Ranking
- ITF = ITF entry
- JE = Junior Exempt
- w/o = Walkover
- r = Retired
- d = Defaulted
Draw
First Round | Quarterfinals | Semifinals | Final | ||||||||||||||||||||||||
1 | 6 | 3 | [10] | ||||||||||||||||||||||||
3 | 6 | [8] | 1 | 6 | 3 | [10] | |||||||||||||||||||||
6 | 6 | 1 | 6 | [6] | |||||||||||||||||||||||
3 | 1 | 1 | 4 | 77 | [4] | ||||||||||||||||||||||
4 | 6 | 4 | [10] | WC | 6 | 65 | [10] | ||||||||||||||||||||
3 | 6 | [4] | 4 | 4 | 4 | ||||||||||||||||||||||
4 | 4 | WC | 6 | 6 | |||||||||||||||||||||||
WC | 6 | 6 | WC | 3 | 3 | ||||||||||||||||||||||
PR | 77 | 6 | 6 | 6 | |||||||||||||||||||||||
WC | 65 | 1 | PR | 3 | 5 | ||||||||||||||||||||||
WC | 4 | 2 | 3 | 6 | 7 | ||||||||||||||||||||||
3 | 6 | 6 | 3 | 2 | 4 | ||||||||||||||||||||||
6 | 6 | 6 | 6 | ||||||||||||||||||||||||
4 | 4 | 6 | 6 | ||||||||||||||||||||||||
61 | 3 | 2 | 3 | 4 | |||||||||||||||||||||||
2 | 77 | 6 |
gollark: Rust's async things, for instance, *may* implode if you run a blocking task in a normal async thing instead of using the dedicated threadpool for it.
gollark: In the case where it's a language runtime doing it it is quite possibly just doing cooperative multitasking internally, yes.
gollark: These have been known to exist, yes.
gollark: Thusly, modern runtimes or high performance applications will do stuff asynchronously, where they just wait for arbitrary amounts of events at once in a small threadpool.
gollark: However, this is inefficient. If you want to serve 12904172408718240 concurrent connections, you don't want to have one thread for each, especially if each one isn't used that much.
References
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.