Search results

From APIDesign

Jump to: navigation, search

There is no page titled "APIDesignPatterns:Performance".

For more information about searching APIDesign, see Help.

Showing below 16 results starting with #1.


View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500)

No page title matches

Page text matches

  1. OlderBlogPosts (111,273 bytes)
    365: Is [[Builder]] better [[APIDesignPatterns|pattern]] than [[CumulativeFactory]]? As Radim an...
    369: ==== Cumulative Factory [[APIDesignPatterns|API Design Pattern]] ====
    371: ... [[APIDesignPatterns|API Design Pattern]]. Read [[APIDesignPatterns:CumulativeFactory|more]]...
    384: Casper Bang asked following question about [[APIDesignPatterns:Exceptions|exceptions in API]] after reading the ...
    388: ...estion! Inspiring. Here are my current answers: [[APIDesignPatterns:Exceptions|exceptions in API]].
  2. Blogs:JaroslavTulach:Practical Design (18,183 bytes)
    153: ...important to cover this pattern in my [[:Category:APIDesignPatterns|API Design Patterns]] Collection.
    278: ... by using [[trait]]s, one can easily get the same performance while keeping encapsulation in modern object orie...
    280: ...eps encapsulation and maintains the C linked list performance. [[C++]] is not as bad as I thought.
  3. Amoeba Model (4,988 bytes)
    3: ...or it be acceptably fast - e.g. have a [[good]] [[performance]]. Almost always we want the application to not c...
    34: ...guage - for example they know and use the right [[APIDesignPatterns]].
  4. Good Name (1,833 bytes)
    3: ...ology with. If widely known, just like names of [[APIDesignPatterns|design patterns]], then it is enough to say that ...
    11: ...stment fond with such [[Good Name]] and very poor performance.
  5. AlternativeBehavior (6,943 bytes)
    121: ...'sumRange''' implementation will benefit from the performance boost. Moreover
    134: [[Category:APIDesignPatterns]]
    135: [[Category:APIDesignPatterns:Evolution]]
  6. Privileged API (3,501 bytes)
    15: ...''Runnable'' objects being created. This may hurt performance and as such one may want the ''lock''/''unlock'' ...
    39: [[Category:APIDesignPatterns]] [[Category:APIDesignPatterns:Creational]]
  7. CacheForModularity (4,221 bytes)
    1: ...[modularity]] and how it affects and relates to [[performance]]. As noted in [[Modular_Java_SE#False_Expectatio...
    125: [[Category:APIDesignPatterns:Performance]]
  8. CompileTimeCache (8,107 bytes)
    41: ...le optimization can dramatically boost start up [[performance]] of your framework.
    65: ...y a lot of [[API]] as well as make it much more [[performance|efficient]].
    69: ...tegory:APIDesignPatterns:Performance]] [[Category:APIDesignPatterns]]
  9. ExtendingInterfaces (3,563 bytes)
    37: ...g/openide/text/NbDocument.java did] to optimize [[performance]] of finding most recently active editor.
    39: Indeed this is not really the best [[APIDesignPatterns|pattern]] to start with, it is better to count wi...
    41: [[Category:APIDesignPatterns]] [[Category:APIDesignPatterns:Evolution]]
    42: [[Category:APIDesignPatterns:Anti]]
  10. Startup (5,923 bytes)
    24: [[Performance]] point of view conclusion: Don't pay attention t...
    43: Conclusion #2: From [[performance]] perspective, there is nothing to optimize in th...
    54: ...ver such applications are likely small. Usually [[performance]] is not an issue.
    64: [[Performance]] point of view: This is the most important useca...
    79: ...dilema: Optimize for this case or not? [[NetBeans:Performance]] team has given up on this usecase in a hope
  11. OrderOfElements (7,000 bytes)
    46: ...itimate reasons why this change had to be done ([[performance]] comes to my mind).
    81: ...Category:APIDesignPatterns:Evolution]] [[Category:APIDesignPatterns:Anti]]
  12. Hammer (4,962 bytes)
    7: ... apply similar practice, we can just follow the [[APIDesignPatterns|pattern]], but in order to do so, we should recog...
    23: The [[performance]] of the new system is certainly better in the ol...
    33: [[Category:APIDesignPatterns:Anti]]
  13. ChameleonBuilder (6,213 bytes)
    68: ... during execution. Thus the performance of this [[APIDesignPatterns|API Design Pattern]] is the same of plain builder...
    86: ... a single return type in [[Java]]. As such this [[APIDesignPatterns|API pattern]] only works for a single ''essential...
    105: [[Category:APIDesignPatterns]]
    106: [[Category:APIDesignPatterns:Creational]]
    107: [[Category:APIDesignPatterns:Exceptions]]
  14. APIReviews (8,646 bytes)
    10: ...stion to choose different solution, improve the [[APIDesignPatterns|implementation methodologies]], [[APIDevelopment#...
    13: [[performance]] implications.
  15. BinaryCompatibleDefaultMethods (6,828 bytes)
    106: ...q.isEmpty()''. But does that matter? Not from a [[performance]] perspective - every [[good]] [[JIT]] compiler e...
    125: [[Category:APIDesignPatterns]]
    126: [[Category:APIDesignPatterns:Evolution]]
  16. TransactionalDataStructure (4,138 bytes)
    19: ...p/ProxyLookup.java#L434 however my problem wasn't performance (btw. the code still uses '''synchronized'''), bu...
    37: [[Category:APIDesignPatterns]]

View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500)



Search in namespaces:

List redirects
Search for
Views
Personal tools
buy