PHP Soap client request time measurement
up vote
0
down vote
favorite
I want to get for each call I do with Soap client a total time
for the request.
I've searched everywhere for such in-the-box solution like curl_getinfo
but nothing.
Tried to log the __getLastResponseHeaders()
and __getLastRequestHeaders()
- no info there about that (and yes- I had enabled the trace).
Is there another solution but to use microtime
for measuring the request time?
php soap-client
add a comment |
up vote
0
down vote
favorite
I want to get for each call I do with Soap client a total time
for the request.
I've searched everywhere for such in-the-box solution like curl_getinfo
but nothing.
Tried to log the __getLastResponseHeaders()
and __getLastRequestHeaders()
- no info there about that (and yes- I had enabled the trace).
Is there another solution but to use microtime
for measuring the request time?
php soap-client
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I want to get for each call I do with Soap client a total time
for the request.
I've searched everywhere for such in-the-box solution like curl_getinfo
but nothing.
Tried to log the __getLastResponseHeaders()
and __getLastRequestHeaders()
- no info there about that (and yes- I had enabled the trace).
Is there another solution but to use microtime
for measuring the request time?
php soap-client
I want to get for each call I do with Soap client a total time
for the request.
I've searched everywhere for such in-the-box solution like curl_getinfo
but nothing.
Tried to log the __getLastResponseHeaders()
and __getLastRequestHeaders()
- no info there about that (and yes- I had enabled the trace).
Is there another solution but to use microtime
for measuring the request time?
php soap-client
php soap-client
asked Nov 22 at 14:59
shemaya
8619
8619
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Well PHP works in sync way anyways. it wont continue untill it has completed a function.
Just add time mes in your code.
// Start of code
$now = microtime(true); // Gets microseconds
// Rest of code
// End of code
echo "Time Elapsed: ".(microtime(true) - $now)."s";
You can pretty much use this anywhere.
or you could do excact curl req via command line: time curl http://www.example.com/
It times the whole request, including network latency.
In a commend line of PHP file would be time php dancebattle.php
There is a general liberally ment for that aswell: https://github.com/fotuzlab/appgati ( it unix only tho, so it wont work on windows)
Anyways, the best and most easy to use is microtime php built in function. I would personally stick with that.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Well PHP works in sync way anyways. it wont continue untill it has completed a function.
Just add time mes in your code.
// Start of code
$now = microtime(true); // Gets microseconds
// Rest of code
// End of code
echo "Time Elapsed: ".(microtime(true) - $now)."s";
You can pretty much use this anywhere.
or you could do excact curl req via command line: time curl http://www.example.com/
It times the whole request, including network latency.
In a commend line of PHP file would be time php dancebattle.php
There is a general liberally ment for that aswell: https://github.com/fotuzlab/appgati ( it unix only tho, so it wont work on windows)
Anyways, the best and most easy to use is microtime php built in function. I would personally stick with that.
add a comment |
up vote
1
down vote
accepted
Well PHP works in sync way anyways. it wont continue untill it has completed a function.
Just add time mes in your code.
// Start of code
$now = microtime(true); // Gets microseconds
// Rest of code
// End of code
echo "Time Elapsed: ".(microtime(true) - $now)."s";
You can pretty much use this anywhere.
or you could do excact curl req via command line: time curl http://www.example.com/
It times the whole request, including network latency.
In a commend line of PHP file would be time php dancebattle.php
There is a general liberally ment for that aswell: https://github.com/fotuzlab/appgati ( it unix only tho, so it wont work on windows)
Anyways, the best and most easy to use is microtime php built in function. I would personally stick with that.
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Well PHP works in sync way anyways. it wont continue untill it has completed a function.
Just add time mes in your code.
// Start of code
$now = microtime(true); // Gets microseconds
// Rest of code
// End of code
echo "Time Elapsed: ".(microtime(true) - $now)."s";
You can pretty much use this anywhere.
or you could do excact curl req via command line: time curl http://www.example.com/
It times the whole request, including network latency.
In a commend line of PHP file would be time php dancebattle.php
There is a general liberally ment for that aswell: https://github.com/fotuzlab/appgati ( it unix only tho, so it wont work on windows)
Anyways, the best and most easy to use is microtime php built in function. I would personally stick with that.
Well PHP works in sync way anyways. it wont continue untill it has completed a function.
Just add time mes in your code.
// Start of code
$now = microtime(true); // Gets microseconds
// Rest of code
// End of code
echo "Time Elapsed: ".(microtime(true) - $now)."s";
You can pretty much use this anywhere.
or you could do excact curl req via command line: time curl http://www.example.com/
It times the whole request, including network latency.
In a commend line of PHP file would be time php dancebattle.php
There is a general liberally ment for that aswell: https://github.com/fotuzlab/appgati ( it unix only tho, so it wont work on windows)
Anyways, the best and most easy to use is microtime php built in function. I would personally stick with that.
answered Nov 22 at 15:21
Comirdc
39614
39614
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433626%2fphp-soap-client-request-time-measurement%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown