Performance impact on using too much try catch block

Question

I have several questions here:
1. The system that I'm developing requires to be high performance, but I am not sure how will try catch block affect overall performance.
2. I wanted to know which would be more efficient (result in faster processing)
Have several generic try catch OR catch all exceptions individually?
ex:
try {
} catch (Exception e){
}vs.
try{
} catch (MalformedUrlException me){
} catch(SQLException){
}3. Which one would be faster, one big try catch block or several small try catch blocks?
ex.
try{
//read from io file
//query database
//parse data
//write to file
//query database again
} catch(Exception e){
//log exception
}vs.
try{
//read from io file
} catch(FileNotFoundException fnfe){
//log exception
try{
//query database
}catch(SQLException se){
//log exception
try{
//parse data
}catch(SaxParserException saxe){
//log exception
try{
//query database again
}catch(SQLException se2){
//log exception
try{
//write to file
} catch(FileNotFoundException fnfe){
//log exception

Answer 1

1. The system that I'm developing requires to be high performance, but I am not sure how will try catch block affect overall performance.Compared to what? You can't write an equivalent program that doesn't have a try-catch block, so the answer would have to be that it doesn't affect performance at all.
2. I wanted to know which would be more efficient (result in faster processing)Have several generic try catch OR catch all exceptions individually?
You still have it backwards. Do you need to do different things for different exceptions? If so, then that's what you have to do and there is no other code that might be "faster".
Here's what you should do. Write the code that needs to be written. Don't leave out necessary stuff because of performance reasons. (If you left out all your code, the program would run much faster.) Then find out which parts of the program ACTUALLY take the most time and work on speeding them up.