Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    Qt Mobility is SLOW!!

    Reply
    admiral0 | # 1 | 2011-02-15, 20:45 | Report

    I get 10 SMS ids with filters, then retrieve message and message body + sender.

    Timed result? ~17secs. That's unacceptable.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    rm42 | # 2 | 2011-02-15, 20:53 | Report

    Originally Posted by admiral0 View Post
    I get 10 SMS ids with filters, then retrieve message and message body + sender.

    Timed result? ~17secs. That's unacceptable.
    Are you running it in a single core (old generation) phone? All new smart phones are going to be running on multi-core hardware. (Except for WP7 phones of course, since that OS still can't handle them.)

    Edit | Forward | Quote | Quick Reply | Thanks

     
    admiral0 | # 3 | 2011-02-15, 20:56 | Report

    Originally Posted by rm42 View Post
    Are you running it in a single core (old generation) phone? All new smart phones are going to be running on multi-core hardware. (Except for WP7 phones of course, since that OS still can't handle them.)
    -.-

    It's not raw power issue, but optimization. How do you expect apps in Qt on N900 when Qt Mobility is so damn slow?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    rm42 | # 4 | 2011-02-15, 21:06 | Report

    Originally Posted by admiral0 View Post
    -.-

    It's not raw power issue, but optimization. How do you expect apps in Qt on N900 when Qt Mobility is so damn slow?
    What I am saying is that your new app will run fine in new generation phones. Also, It will be quite easy to optimize Qt Mobility to be faster by then.

    Then again, if PlanB does not get implemented, you have bigger things to worry about if you are a Qt programmer.

    Edit | Forward | Quote | Quick Reply | Thanks

     
vBulletin® Version 3.8.8
Normal Logout