Hello,
i'v startet to create a connection via services3 REST-Server to/from my php-driven website (at this time both my-site and drupal are on same machine).
I noticed that if i use/connect via services3 node.login enormous CPU usage about 30%-70%, normaly on my machine is between 0-10% (MAX).
i made different test with Apache Jmeter:
login/logout via normal drupal site(drupal form-login) cpu usage low, as expected
when i use http://drupal-site.tld/services_api/user/login (logout) the CPU usage increases by 30%-70% and that is too much!
enabling under performance settings "use cache" in drupal makes no difference, even activated APC+memcached makes no difference
my "workflow" is:
i use drupal for bloging to an existing website and wanted to make this via the services/rest api
for ex:
user login
create node, edit node, list all nodes for logged in user...
user logout
my test case are:
apache+php5_mod
nginx+php-fpm
on both same result
is it the problem that i'v 400connects per second and every connect makes an user.login; get all blogs off loggedin user (show on site); user.logout via services3/rest?
so where is the bottleneck, is there a bug in services3, how can i debug to get near the bad code
tnx for Help!