fred rosenberger

What have you tried?  What did it do different than what you expected?

Frank Jacobsen wrote:
Faster = The fastest way this can be done.

If you really want "The fastest way this can be done", buy a better cpu. Then wait a few months, and there will be even BETTER hardware, so you can then that to get more speed...etc.  Make sure you kill all other processes on whatever machine you are running so nothing else steals CPU time. If you are bound by disk reads, get a better disk drive.  and so on...

What we're trying to get at is that this is not a spec.  Something can always be done to make it faster. The question becomes "Is it worth it to make it faster than it is now?"  and/or "how fast is fast enough?".  If it can process each call in 10 microseconds, is it worth it to spend $1,000,000 to get it down to 9 microseconds?  That would be faster.  Then do you spend another $2million to get it down to 8?

Best practices say you define what the speed needs to be before you start optimizing. Then you look at where your bottlenecks are, what it would take to improve each, and at what cost.  Then you decide which ones are worth the cost.  

"The fastest way it can be done" is an unobtainable goal, as there is (for all intents and purposes) no end point.

The best solution for doing things "fastest" is to buy better hardware - CPUs, memory, etc.

or look at the table where it says:

100 99.99997%

Sami radwan wrote:all my objects should be declared final?

It's confusing. I had a hard time as a beginner with this concept.  When you have a line like:

Person person = New Person();

there are two things create.  "New Person()" creates a Person object somewhere off in memory.  "Person person" creates a reference to an object of type Person.

I think of it as the reference being a card in a rolodex, where you write down the address of a house.  And the Person object is the house itself.  If you make your "person" reference final, you are writing the address in ink - it cannot be changed later.  That's not to say you can't go to the house the address points to and paint it a new color...

I second Campbell's question.  Are you assuming a CSV file will be faster for some reason?  The first rule of optimization is NEVER ASSUME one way will be better.

Databases are a pretty mature technology.  The have been honed and tuned for decades to give excellent performance, doing things you are often not even aware.  I would be surprised if parsing a CSV file would be faster than a DB query.

Also, if you are only exporting the data once, does it matter how fast it is?  Had you just started an export three days ago when you created this thread, it might be done by now.  Does the speed of the EXPORT really matter, when compared to the searching time?

and as to your "is it possible..." question, the answer is always "yes, but....".  Yes, you can, given enough time, effort, and money.  A better question is "Is it worth it...", and honestly it seems like "No" is the answer.

Alireza Saidi wrote:Hello dear friend! How can I solve that? Can you help me please?

People here love to help you, but they won't do it for you.  You need to tell us what exactly the problem is.  Does this compile? does it run?  does it give the wrong output?

tell us the details.  Ask questions.  engage with people who post, and you will get more help than you could ever ask for.

I always think it's a good idea to talk you your manager.  I meet with mine at least every two weeks.  

Regarding your specific problem, don't just go in and say "I have too much work." Go in with some kind of plan for how to address it.  Have a prioritized list of all your tasks, and work with your manager to be sure you both agree.  Or create a schedule, saying "i can spend X hours a day on this, and Y hours on that".  Be sure to leave in some time for things like company meetings, emails, etc.

A good manager should be willing to work with you.  It's not their job to solve all your problems, but to be a partner.  You want to try and set expectations sooner rather than waiting for things to blow up,

The best way to tell if something will compile is to compile it.  That gives you the definitive answer.

Stephan van Hulst wrote:What I like about your example Fred, is that most people would probably still intuitively say that it doesn't matter, and that the final choice has a 50% chance of picking the door with the car.

These are the same people who say they have a 50-50 chance of winning vs. losing the lottery.

I like the fact that a good way to get a grip on this problem is to make it MORE complicated...sort of.  Often to understand a problem you reduce the number of options.  But in this case....

Imagine there are a million doors, with a car behind one and a goat behind the rest.  

You pick a door.

The host opens ALL THE OTHER DOORS BUT ONE, and all show a goat.

Now do you switch?

Matthew Bendford wrote:unrelated side-note:Trying to read screenshots often is hard on such small screens.

I'm on a laptop with a widescreen monitor, and I have a hard time reading screenshots, too.  Some of us are just old.

When just starting out, one of your BEST friends is "System.out.println".

When something isn't working like you'd expect, throw some of those bad boys in.  If "total" isn't what you think it should be, print out its value every time it changes. Using it is a great way to see what's happening beneath the cover, so to speak.

I may be wrong here, but I'm not sure you CAN get a list of certificates from a command prompt. Couldn't each browser you use have its own set of root certs?

well..if you change "<=" to "=", you are changing it from a comparison to an assignment. You probably would want "==".