Siege performance test Result parameter problem

I'm using siege to test one of my Web sites and enter the following commands

siege -c 10 -r 10 -f test.txt

Then we get the following result:

Transactions:                1300 hitsAvailability:              100.00 %Elapsed time:                3.99 secsData transferred:            0.54 MBResponse time:                0.01 secsTransaction rate:          325.81 trans/secThroughput:                0.13 MB/secConcurrency:                2.82Successful transactions:         100Failed transactions:               0Longest transaction:            1.04Shortest transaction:            0.00

I would like to ask, why is this transactions 1300 instead of 100? Does reponse time mean the average response times? Concurrency max concurrency is the maximum concurrency that it can estimate for a website?
How to use siege to log in before testing?

Reply content:

I'm using siege to test one of my Web sites and enter the following commands

siege -c 10 -r 10 -f test.txt

Then we get the following result:

Transactions:                1300 hitsAvailability:              100.00 %Elapsed time:                3.99 secsData transferred:            0.54 MBResponse time:                0.01 secsTransaction rate:          325.81 trans/secThroughput:                0.13 MB/secConcurrency:                2.82Successful transactions:         100Failed transactions:               0Longest transaction:            1.04Shortest transaction:            0.00

I would like to ask, why is this transactions 1300 instead of 100? Does reponse time mean the average response times? Concurrency max concurrency is the maximum concurrency that it can estimate for a website?
How to use siege to log in before testing?

