Hello @d13co . Thank you again for the solution you provided me. It helped a lot! I would like to share my experience with you.
When using goal clerk rawsend (goal clerk send) for sending transactions, any batch of 1000 or fewer transactions always appeared in one block. When I scaled up to 10,000 transactions, my batch was spread across four non-consecutive blocks in some cases. As one example, here are the blocks that included the transactions sent by me in one batch of 10,000:
40696332 : 9650 txns.
40696333 : 334 txns.
40696334 : 5 txns.
40696336 : 20 txns.
Some of my transactions experienced a 13-second transaction confirmation time (response time). I cannot figure out why Algorand does not fit all of the 10,000 transactions into one block, also why the blocks are non-consecutive. Where might the bottleneck be? Might there a bottleneck somewhere before the block proposal assembly phase?
I am watching: https://www.youtube.com/watch?v=hbT2SmrouIA (and notably the figure at time 9:44) to better understand Algorand performance.
I am happy to share my code and any findings that I have. My goal is to build a queueing model of Algorand.
Thank you again for your insights.