Performance"

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

(New page: Performance in V3 has many different faces. It impacts in several aspects that end up by giving our end users a smooth and pleasant experience. Here we are naming some of the performance ...)
 
 
Line 1: Line 1:
Performance in V3 has many different faces. It impacts in several aspects that end up by giving our end users a smooth and pleasant experience.
+
__NOTOC__Performance in V3 has many different faces. It impacts in several aspects that end up by giving our end users a smooth and pleasant experience.
  
 
Here we are naming some of the performance aspects to consider. But, it is always important to properly weight things well, to not abuse on performance enhancements.
 
Here we are naming some of the performance aspects to consider. But, it is always important to properly weight things well, to not abuse on performance enhancements.
Line 9: Line 9:
 
While developing, profiling the code must be part of our everyday work. Optimization points must be constantly identified, and performance fixes applied to the code, to enhance its execution time and reduce the number of calls. This is a win win solution.
 
While developing, profiling the code must be part of our everyday work. Optimization points must be constantly identified, and performance fixes applied to the code, to enhance its execution time and reduce the number of calls. This is a win win solution.
  
[[FCKeditor_3.x/Design_and_Architecture/Development_Methodology#KISS|KISS]]: less code performs better, usually.
+
[[FCKeditor 3.x/Design and Architecture/Development Methodology#KISS|KISS]]: less code performs better, usually.
  
 
== Fast Download ==
 
== Fast Download ==

Latest revision as of 00:05, 5 February 2008

Performance in V3 has many different faces. It impacts in several aspects that end up by giving our end users a smooth and pleasant experience.

Here we are naming some of the performance aspects to consider. But, it is always important to properly weight things well, to not abuse on performance enhancements.

Fast Code Execution

JavaScript and DOM targeted development are synonymous of "bad performance", when compared with other development technologies. For the development of V3 we must be "performance maniacs" to compensate the language and platform limits, bringing a better user experience.

While developing, profiling the code must be part of our everyday work. Optimization points must be constantly identified, and performance fixes applied to the code, to enhance its execution time and reduce the number of calls. This is a win win solution.

KISS: less code performs better, usually.

Fast Download

Our project is quite complex. This complexity results in an also complex and huge code base. No only, V3 is a user interface component, and therefore it includes typical UI elements, like images and dialogs.

Our goal is putting all the necessary things needed to run V3 together, and deliver it in the minimum amount of time, reducing download sizes and the number of requests to the server.

We'll be constantly researching code minification and design strategies that can help us bringing the best results in this area.

Fast Startup

Fast download reflects on faster startup. But also our code, and the design of V3 must consider the startup speed as a key thing to make our users satisfied. This is the thing that brings the real "lightweight" sensation to V3.

Fast DOM

When introducing DOM elements to a document, specific performance strategies must be considered. Some elements perform better than others. A simpler DOM structure also performs better. The proper usage of CSS techniques can help making things simpler and faster, while providing a design rich user interface.


This page was last edited on 5 February 2008, at 00:05.