Databases
StackOverflow2013
Postsdbo
POShould I always make my java-code thread-safe, or for performance-reasons do it only when needed?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POShould I always make my java-code thread-safe, or for performance-reasons do it only when needed?
    primarykey
    data
    text
    <p>If I create classes, that are used at the moment only in a single thread, should I make them thread-safe, even if I don't need that at the moment? It could be happen, that I later use this class in multiple threads, and at that time I could get race conditions and may have a hard time to find them if I didn't made the class thread-safe in the first place. Or should I make the class not thread-safe, for better performance? But premature optimization is evil.</p> <p>Differently asked: Should I make my classes thread-safe if needed (if used in multiple threads, otherwise not) or should I optimize this issue then needed (if I see that the synchronization eats up an important part of processing time)?</p> <p>If I choose one of the both ways, are there methods to reduce the disadvantages? Or exists a third possibility, that I should use?</p> <p><strong>EDIT</strong>: I give the reason this question came up to my mind. At our company we have written a very simple user-management that writes the data into property-files. I used it in a web-app and after some work on it I got strange errors, that the user-management forgot about properties of users(including name and password) and roles. That was very annoying but not consistently reproducible, so I think it was race condition. Since I synchronized all methods reading and writing from/on disk, the problem disappeared. So I thought, that I probably could have been avoided all the hassle, if we had written the class with synchronization in the first place?</p> <p><strong>EDIT 2</strong>: As I look over the tips of Pragmatic Programmer, I saw tip #41: Always Design for Concurrency. This doesn't say that all code should be thread-safe, but it says the design should have the concurrency in mind.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAlex Miller
    1. USMnementh
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POShould I always make my java-code thread-safe, or for performance-reasons do it only when needed?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POShould I always make my java-code thread-safe, or for performance-reasons do it only when needed?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POShould I always make my java-code thread-safe, or for performance-reasons do it only when needed?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSomething to help out your analysis is to not think of concurrency as premature optimization, but rather a performance concern akin to BigO. The premature optimization-is-evil observations are in reference to people unrolling loops or cryptic switch-if conditional constructs in C/C++ that are impossible to decipher and maintain, and may not give you any performance gain after the compiler is through with the code (or in java the runtime JIT).
      singulars
      1. POShould I always make my java-code thread-safe, or for performance-reasons do it only when needed?
      1. USreccles
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload