Well, if you query large chunks of raw data and process it yourself, no wonder that you get faster response times...
However in your example you end up with a raw encoded transaction, in the "obvious" case you have a nicely decoded transaction in JSON format... if I needed high speeds + python I'd rather use something like pynode or let Armory do the parsing for me, if I were just trying out stuff, the few GB or RAM or SSD space for the index are much cheaper than me writing a raw transaction decoder.
Topic: Blog post: Fast blockchain scanning (Read 839 times)
This is something that we'll be needing soon. Thanks 
Interesting, thanks!
I just added a blog post about faster blockchain scanning through bitcoind RPC calls, by replacing gettransaction queries per transaction with getblock false and DIY block and transaction decoding.
The blog post is here:
http://upcoder.com/8/fast-blockchain-scanning/
Feedback welcome.
Thomas
The blog post is here:
http://upcoder.com/8/fast-blockchain-scanning/
Feedback welcome.
Thomas
Jump to: