Category:APIDesignPatterns:Performance
From APIDesign
(Difference between revisions)
(New page: Designing APIs to have good performance - e.g. to execute quickly, and not over-consume various resources - is harder than optimizing a single in-house application. Here is few tri...) |
|||
| (One intermediate revision not shown.) | |||
| Line 1: | Line 1: | ||
| - | Designing [[API]]s to have good [[performance]] - e.g. to execute quickly, and not over-consume various resources - is harder than optimizing a single in-house application. Here is few tricks to make it easier. | + | Designing [[API]]s to have good [[performance]] - e.g. to execute quickly, and not over-consume various resources - is harder than optimizing a single in-house application. Here is few tricks to make it easier. Majority of these tricks has been invented while I was serving in the [[netbeans:performance|NetBeans Performance]] team. In case you are looking for other, not primarily [[API]] related [[performance]] advices, visit the [[netbeans:performance]] wiki. |
| + | |||
| + | [[Category:APIDesignPatterns]] | ||
Current revision
Designing APIs to have good performance - e.g. to execute quickly, and not over-consume various resources - is harder than optimizing a single in-house application. Here is few tricks to make it easier. Majority of these tricks has been invented while I was serving in the NetBeans Performance team. In case you are looking for other, not primarily API related performance advices, visit the netbeans:performance wiki.
Pages in category "APIDesignPatterns:Performance"
There are 3 pages in this category.
Follow
