• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Knute Snortum
  • Junilu Lacar
  • Devaka Cooray
Saloon Keepers:
  • Ganesh Patekar
  • Tim Moores
  • Carey Brown
  • Stephan van Hulst
  • salvin francis
Bartenders:
  • Ron McLeod
  • Frits Walraven
  • Pete Letkeman

Bottle neck  RSS feed

 
Ranch Hand
Posts: 120
Eclipse IDE Flex Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am currently wring a spring app for my back end. I am using RMI to expose the app. And then I am using Swing as my front end and using RMI to consume it.

Where are the bottle necks in spring?

I ask this because I am trying to decide which is better. To get a masters detail list all at once from the database or each time from the front end? While we test a master detail relationship, we do somewhat iterate through the list but when users do such a thing, I am not so sure they would iterate through. But as I was considering this, I realized I really need to know where the bottle neck is to determine which is best under certain circumstances. For example, maybe the overhead of getting the context is so severe that its better to get the detail lists at once. Or maybe not. Anyone know any data about this?
 
author & internet detective
Marshal
Posts: 38687
677
Eclipse IDE Java VI Editor
  • Likes 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Spring is just a framework. The bottleneck is going to depend on the details of your application. In a well designed application, accessing the database is traditionally the bottleneck.

How big is your master list? This will be a factor in your decision because you are trading off speed for memory.

The nice thing is that it is easy to add caching later. You can always query each time and add caching in later if that turns out to be the bottleneck. And an unacceptable bottleneck at that. If your bottleneck takes .5 seconds and the UI returns in .6 seconds, you may decide this is acceptable.
 
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!