Your SlideShare is downloading. ×
Web  performance
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Web performance

287
views

Published on

what's thing we should think about during the performance journey . Major help you to solve these problem .

what's thing we should think about during the performance journey . Major help you to solve these problem .

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
287
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Web PerformanceOptimization
  • 2. Agenda
    What?
    Why?
    How?
  • 3. What does it looks like?
    What?
  • 4. Long and Hard Journey
  • 5. Q: what’s the trip destination?
    Palo Alto ?
    CDC ?
    Sweden?
    Indian ?
  • 6. Why?
  • 7. Language Level
    Most compilers in most programmer
    languages does these optimizations
    for you, but not JavaScript.
  • 8. Structure Level
    Requirement and Design change, some
    time need restructure and redesign our
    Program .
  • 9. Coding Level
    Developer skills are difference, implement
    ways are different, but just one way is the
    best.
  • 10. The most Important one:
    Improve User Experience, make user happy.
  • 11. How?
  • 12. Structure meet the requirement
    Suggestion:
    When we design the structure , we should think about the data size, if the at the beginning of the project, the spec could provide some information of data size we should support, like min / max data size, that
    could help us more.
  • 13. Correctness First
    Correctness First, then do optimize
    Test Performance early(when coding, don’t forget the performance)
    More Testing (Different Browser IE8, FF3/4)
  • 14. When server response slow, what’s the first thing we think about?
    Server Slow?
    Request parameters too much?
    varobjParams = {
    ids: cb.args()[0],
    paramQueryParams: {
    retrieveParamGroups: true,
    retrieveParams: true,
    objGroupQueryParams: { retrieveObjectGroups: true,
    retrieveObjectGroupMembers: true
    } },
    retrieveTags: true };
  • 15. Suitable Operation Interfacewith Back-end
  • 16. Why big data at one time?
  • 17. Back-end
    Front-end
    Data size
    response
    Request
    1
    2
  • 18. If necessary , don’t forget using XSLT process big XML data
  • 19. Don't Optimize Without Measuring
  • 20. A
    B
    C
    D
    Only speed up things that take a lot of time.
  • 21. Avoid unnecessary repaint
  • 22. TODO
  • 23. Code Quality
    High quality code is mostly likely to avoid platform problems.
    Code Conventions for the JavaScript Programming Language
    http://javascript.crockford.com/code.html
    Use JSLint.com. Pass with no warnings.
    Coder refractor
    (https://github.com/kangax/kratko.js)
  • 24. Have regular code readings.
    Don’t wait until release to do code reviews.
    Do team code reading regularly during development.
    Experienced developers can lead by example.
    Novice developers learn from the group.
    Problems can be discovered early.
    Good techniques can be shared early.
  • 25. Questions?
    What’s the destination of our
    long and hard journey?
  • 26. About Author
    Name: Major
    Email: major.yezhouquan@gmail.com
    City: Beijing / China
  • 27. Thanks