1.0.0.(Alpha5) high CPU usage with XMPP daemon plugin

Great work StatusNet team! Wonderful project and features!

One problem, high CPU usage with XMPP daemon plugin...
we cannot run it at that high CPU, so disabled XMPP in config.php so we have no bot :-(

Any ideas on how to find the cause of this, no error logs or anything that we can find.

Comments

  • XMPP is untested with 1.0.x alpha so far, it's very possible that it will not behave as expected.
  • Thanks, anything we can do to help test or debug or anything?
  • I'm not too sure, I think it probably stems from the improved privacy settings we have in 1.0.x and the current xmpp integration not being aware of it.
  • We rely a lot on the bot for interaction with Pidgin and old mobiles (Talkonaut) so getting this fixed would be a priority for us, if you have any ideas if we can help.

    Also, there seems to be authentication problems as statusnet desktop no longer works, and also twitter feed API is saying "authorisation failure" whilst it had finally been working on 0.9.7.
  • 1.0.0.beta.2 still loop and high CPU cannot leave bot running, is this something likely to be fixed or which we can help with? Or any work around?
  • Nothing at this time, unfortunately. We are working on cracking down on bugfixes prior to finalizing 1.0 - I am fairly certain this will get some attention.
  • Hi, thanks for reply.
    will wait for 1.0 for using XMPP.

    I upgraded to 1.0.0alpha5 from 0.9.7
    is it possible to downgrade database to 0.9.7-0.9.9?
    in order to to use XMPP.
  • I've never tried downgrading, I'm not sure that it's a good idea.
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Google Sign In with OpenID