Page 2 of 3 FirstFirst 123 LastLast
Results 21 to 40 of 42
Like Tree8Likes
  1. mosdl's Avatar
    Posts
    781 Posts
    Global Posts
    787 Global Posts
    #21  
    Quote Originally Posted by rsanchez1 View Post
    @mosdl: Yes, those things factor in as well, but then HP consistenly using old versions of webkit hurts all those things as well (except memory and network conditions). And actually, it's like saying a browser sucks because it is consistenly slower than the other browsers.
    In my experience with complex web apps, Javascript is never the issue. Browsers get faster, but it shaves a few ms which makes very little difference. Often enough network performance is what slows down webpage loading the most.

    The issue with the Touchpad seems to be related to garbage collection issues, which comes from the multi-tasking aspect of webOS. I believe the PlayBook had these issues too from what I read.

    Should HP have done better? Yes, they need some of the more advanced mark and sweep algorithms, but those are still newish.
    Apps: MyQ for Netflix (Phone/TouchPad), Giantbomb (Phone), Excavate (Reddit/Digg clients for TouchPad)
  2. #22  
    Quote Originally Posted by mosdl View Post
    The issue with the Touchpad seems to be related to garbage collection issues, which comes from the multi-tasking aspect of webOS. I believe the PlayBook had these issues too from what I read.
    are you saying more memory can fix the issue? If no improvement in software aspect.


    -- Sent from my Palm Pre using Forums
  3. #23  
    Quote Originally Posted by mosdl View Post
    In my experience with complex web apps, Javascript is never the issue. Browsers get faster, but it shaves a few ms which makes very little difference. Often enough network performance is what slows down webpage loading the most.

    The issue with the Touchpad seems to be related to garbage collection issues, which comes from the multi-tasking aspect of webOS. I believe the PlayBook had these issues too from what I read.

    Should HP have done better? Yes, they need some of the more advanced mark and sweep algorithms, but those are still newish.
    but then why would playbook gives the same benchmark as IP-2?
    If this helped you hit thanks.
  4. mosdl's Avatar
    Posts
    781 Posts
    Global Posts
    787 Global Posts
    #24  
    The memory issues can be fixed in the webkit engine.

    Playbook reviews said that apps had slowdowns as well. The slowdowns have nothing to do with javascript speed.
    Apps: MyQ for Netflix (Phone/TouchPad), Giantbomb (Phone), Excavate (Reddit/Digg clients for TouchPad)
    fxspec06 likes this.
  5. #25  
    I have NO clue what any of this means, but as a average consumer who has nothing but love for webOS, maybe HP needs to find some engineers who can get it right.

    How can they NOT have used this and didnt notice the simple things you guys are pointing out as well as some of the early reviewers, just sad.
  6. #26  
    Quote Originally Posted by RoverNole View Post
    I have NO clue what any of this means, but as a average consumer who has nothing but love for webOS, maybe HP needs to find some engineers who can get it right.

    How can they NOT have used this and didnt notice the simple things you guys are pointing out as well as some of the early reviewers, just sad.
    Hit it right on the head. Maybe they will post an add for webkit engineer now.
    If this helped you hit thanks.
  7. mosdl's Avatar
    Posts
    781 Posts
    Global Posts
    787 Global Posts
    #27  
    webOS always has had these slowdowns, nothing really new. Its more pronounced perhaps when dealing with the larger screen.
    Apps: MyQ for Netflix (Phone/TouchPad), Giantbomb (Phone), Excavate (Reddit/Digg clients for TouchPad)
  8. mosdl's Avatar
    Posts
    781 Posts
    Global Posts
    787 Global Posts
    #28  
    Also, HP has said a OTA update is coming soon to fix alot of the issues, so we shall see
    Apps: MyQ for Netflix (Phone/TouchPad), Giantbomb (Phone), Excavate (Reddit/Digg clients for TouchPad)
    mikevember, fxspec06 and Rnp like this.
  9. #29  
    Quote Originally Posted by mosdl View Post
    Also, HP has said a OTA update is coming soon to fix alot of the issues, so we shall see
    THIS makes my point in my earlier post, did they not know this before today??
  10. #30  
    Quote Originally Posted by mosdl View Post
    webOS always has had these slowdowns, nothing really new. Its more pronounced perhaps when dealing with the larger screen.
    I've often wondered exactly why webOS seems doomed to remain inconsistent in UX: buttery-smooth one minute, and a laggy, stuttery mess the next.

    The only hardware I've owned thus far that seems to make webOS "truly happy" is the Pre2. Even my Veer, which I adore, feels like a Pre Plus at times. Does this possibly indicate that the hardware specs of Pre2 are the minimum for webOS 2.x (a relatively optimized build) to run well, or am I off-base?

    Given the TouchPad's beefy hardware, is the periodic slowdown something that could go away with enough optimization?
  11. gabe2gg's Avatar
    Posts
    150 Posts
    Global Posts
    165 Global Posts
    #31  
    Quote Originally Posted by mosdl View Post
    Also, HP has said a OTA update is coming soon to fix alot of the issues, so we shall see
    no offense but this seems strangely similar to the pre- launch. HP must realize that first impressions are everything to a consumer new to your platform.
  12. #32  
    Apparently, the Touchpad is currently the only tablet in the market using a Qualcomm processor. Does anyone know how well Snapdragon compares to Tegra 2 and OMAP4 chips at the same clockspeed?
  13. samab's Avatar
    Posts
    743 Posts
    Global Posts
    2,060 Global Posts
    #33  
    Quote Originally Posted by greenoyster View Post
    Apparently, the Touchpad is currently the only tablet in the market using a Qualcomm processor. Does anyone know how well Snapdragon compares to Tegra 2 and OMAP4 chips at the same clockspeed?
    A 1.2 GHz dual core Qualcomm Snapdragon CPU will have the same DMIPS as a 1 GHz dual core Cortex A9 CPU. Snapdragon and OMAP4 both have NEON (SIMD like Intel's SSE). Tegra 2 doesn't have NEON.
  14. #34  
    Quote Originally Posted by mosdl View Post
    The memory issues can be fixed in the webkit engine.

    Playbook reviews said that apps had slowdowns as well. The slowdowns have nothing to do with javascript speed.
    I dont't know, it has 1G memory, I find it hard to believe garbage collector could be such an issue. I guess somebody should write a memory monitor and examine the relationship between free memory and system performance.

    -- Sent from my Palm Pre using Forums
  15. mosdl's Avatar
    Posts
    781 Posts
    Global Posts
    787 Global Posts
    #35  
    Quote Originally Posted by clevin View Post
    I dont't know, it has 1G memory, I find it hard to believe garbage collector could be such an issue. I guess somebody should write a memory monitor and examine the relationship between free memory and system performance.

    -- Sent from my Palm Pre using Forums
    It depends how threaded webos apps are. If they run all on one thread it could be a issue.
    Apps: MyQ for Netflix (Phone/TouchPad), Giantbomb (Phone), Excavate (Reddit/Digg clients for TouchPad)
  16. #36  
    Quote Originally Posted by mosdl View Post
    It depends how threaded webos apps are. If they run all on one thread it could be a issue.
    I wonder if the code for multi-threaded support is even in yet.

    This could explain poor scores and performance problems, which an update would easily fix.
    Neo Enyo 2.0 Twitter App: NOW AVAILABLE | WON REVIEW
    clearview - clear card app for HP TOUCHPAD
    Wild'n Video Poker - AVAILABLE FOR ALL WEBOS DEVICES! | follow for latest updates - @fxspec06

  17. #37  
    Quote Originally Posted by fxspec06 View Post
    I wonder if the code for multi-threaded support is even in yet.

    This could explain poor scores and performance problems, which an update would easily fix.
    I like you, always hopeful
    If this helped you hit thanks.
  18. #38  
    Quote Originally Posted by stung View Post
    apple must be paying the benchmark to be biased
    Doubtful. As a veteran of the enterprise hardware database wars (TPC-A), a platform can be tuned to do well on a specific benchmark. The results don't mean the benchmark is reflective of a real-life usage pattern.

    Still, slowdowns being reported in the reviews suggest there are either memory leaks, a garbage collection issue or both.
    Dan Donovan
  19. #39  
    Quote Originally Posted by nappy View Post
    Does webOS use V8?
    Quote Originally Posted by clevin View Post
    Thats what i heard.

    ---
    galaxy tab tapatalk
    fxspec06 likes this.
  20. #40  
    Quote Originally Posted by kkhanmd View Post
    I like you, always hopeful
    like his post than!!

    kkhanmd likes this.
Page 2 of 3 FirstFirst 123 LastLast

Posting Permissions