memory usage

• 
  Hi Ian,
  
  
  Thanks for getting in touch. Unfortunately at the moment there are some performance/memory usage issues when using large databases. There should be a significant performance increase when version 3 appears, although I can't necessarily guarantee that it won't still use a lot of memory if you're working with very large databases. 700 megs does seem slightly excessive though.
  
  We haven't published any information about version 3 as yet because we're just at the start of the project and are still trying to decide on the scope and feature set. What I can tell you is that it will feature completely new caching and parsing models which should improve its functionality greatly. Beyond that I really can't say at the moment, for which I apologise. Within the next couple of months we are planning to run a beta program for version 3, with the release being sometime in September if all goes well. If you're interested in being a beta tester for the new version please drop me a line at bartDOTreadATredHYPHENgateDOTcom.
  
  
  Many thanks,

  Bart Read June 02, 2006 07:15

  - 0 +
• 

  Bart Read wrote:

  Hi Ian,
  
  
  Thanks for getting in touch. Unfortunately at the moment there are some performance/memory usage issues when using large databases. There should be a significant performance increase when version 3 appears, although I can't necessarily guarantee that it won't still use a lot of memory if you're working with very large databases. 700 megs does seem slightly excessive though.
  
  We haven't published any information about version 3 as yet because we're just at the start of the project and are still trying to decide on the scope and feature set. What I can tell you is that it will feature completely new caching and parsing models which should improve its functionality greatly. Beyond that I really can't say at the moment, for which I apologise. Within the next couple of months we are planning to run a beta program for version 3, with the release being sometime in September if all goes well. If you're interested in being a beta tester for the new version please drop me a line at bartDOTreadATredHYPHENgateDOTcom.
  
  
  Many thanks,

  
  Cheers Bart, That's good to know. I've only experienced the 700meg hit once now, so I think it might have been a bug. Currently it sits at around 50-100meg depending on how many databases I'm connecting to which I can cope with.
  V3 sounds interesting, I'll drop you an email a little later on.
  
  Cheers
  Ian

  Ian June 05, 2006 06:35

  - 0 +
• 
  I am seeing Sql Prompt slow down as it takes up between 150MB -300MB memory. Is there any way I can get in on the beta testing for the Sql Prompt 3 also.
  
  What is considered an acceptable amount of memory used by SQL Prompt2.

  vandal52 June 30, 2006 11:19

  - 0 +
• 
  Hi there vandal52,
  
  
  Thanks for posting. In answer to your question: how long is a piece of string? The amount of memory SQL Prompt 2 uses will be directly proportional to the number of objects in your database.
  
  Let me explain, SQL Prompt 2 caches a great deal of information on disk, as will SQL Prompt 3, although we've completely rewritten the meta-data cache for version 3. There are some similarities though. For example, whilst it's possible to throw most of the meta-data onto disk until it's needed, the model used to populate the candidate list for the database you're currently working on needs to be largely in physical memory in order to keep the responsiveness of the application acceptable. Thus for large databases you'll see greater memory usage. Ironically, the thing with SQL Prompt is that this is even more necessary for larger databases since it is necessary to filter very large amounts of data very quickly. Incidentally version 3 will incorporate a much improved filtering model with much better performance characteristics on large databases than version 2.
  
  All of that said, unless you're dealing with a reasonably large database I would not expect to see SQL Prompt using the amount of memory you're seeing. Is this something you always see when using SQL Prompt, or has it been a one-off? The reason we ask is that we are aware that there is a bug in version 2 that can cause it to thrash the CPU and/or chew threw memory at an alarming rate. However, this isn't terribly reproducible and usually exiting SQL Prompt and restarting it cures the problem.
  
  I hope that helps to give you some insight into what's happening.
  
  
  Many thanks,

  Bart Read June 30, 2006 11:28

  - 0 +

Add comment

Please sign in to leave a comment.