Details
Task
Description
When an ICEmobile application is first viewed, the page may take some time to load.
At JavaOne we saw very long load times for both the carousel and the preview image in mediacast. Also, the page load after a camera upload from ICEmobile-SX was very slow.
Issue Links
- depends on
-
PUSH-205
Optimization for mobile connection limitations
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Reporter | Migration [ remote ] | Ted Goddard [ ted.goddard ] |
| Fix Version/s | 1.2 Final [ 10371 ] |
| Fix Version/s | 1.2 EE [ 10372 ] | |
| Fix Version/s | 1.2 Final [ 10371 ] |
| Assignee | Steve Maryka [ steve.maryka ] | Ted Goddard [ ted.goddard ] |
As stated, this issue is fairly generic, but the specific problem seen at JavaOne is expected to be resolved by PUSH-205.
Show
Ted Goddard
added a comment - As stated, this issue is fairly generic, but the specific problem seen at JavaOne is expected to be resolved by PUSH-205 .
Both Push updates and device-initiated photo uploads are very responsive on iPhone and iPad Container.
Show
Ted Goddard
added a comment - Both Push updates and device-initiated photo uploads are very responsive on iPhone and iPad Container.
Both Push updates and device-initiated photo uploads are very responsive on iPhone and iPad with ICEmobile-SX.
Show
Ted Goddard
added a comment - Both Push updates and device-initiated photo uploads are very responsive on iPhone and iPad with ICEmobile-SX.
Marking as resolved since the main performance problem was due to PUSH-205 which is now fixed in this release. Specific JIRAs can be created for other optimization tasks.
Show
Ted Goddard
added a comment - Marking as resolved since the main performance problem was due to PUSH-205 which is now fixed in this release. Specific JIRAs can be created for other optimization tasks.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 1.3 Beta [ 10373 ] |
If icepush.jar is removed from the mediacast application, performance on the iPhone increases dramatically. This step was prompted by earlier network analysis that showed the the GET request for a recent image added to the page is not made until the ICEpush noop returns. In other words, the Safari browser is using a small number of sockets (likely 2) for all network activity and any particular request can be randomly stalled behind the push blocking connection.