Databases
StackOverflow2013
Postsdbo
POC# Object Pooling Pattern implementation
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POC# Object Pooling Pattern implementation
    primarykey
    data
    text
    <p>Does anyone have a good resource on implementing a shared object pool strategy for a limited resource in vein of Sql connection pooling? (ie would be implemented fully that it is thread safe).</p> <p>To follow up in regards to @Aaronaught request for clarification the pool usage would be for load balancing requests to an external service. To put it in a scenario that would probably be easier to immediately understand as opposed to my direct situtation. I have a session object that functions similarly to the <code>ISession</code> object from NHibernate. That each unique session manages it's connection to the database. Currently I have 1 long running session object and am encountering issues where my service provider is rate limiting my usage of this individual session.</p> <p>Due to their lack of expectation that a single session would be treated as a long running service account they apparently treat it as a client that is hammering their service. Which brings me to my question here, instead of having 1 individual session I would create a pool of different sessions and split the requests up to the service across those multiple sessions instead of creating a single focal point as I was previously doing.</p> <p>Hopefully that background offers some value but to directly answer some of your questions:</p> <p><strong>Q:</strong> Are the objects expensive to create?<br> <strong>A:</strong> No objects are a pool of limited resources</p> <p><strong>Q:</strong> Will they be acquired/released very frequently?<br> <strong>A:</strong> Yes, once again they can be thought of NHibernate ISessions where 1 is usually acquired and released for the duration of every single page request.</p> <p><strong>Q:</strong> Will a simple first-come-first-serve suffice or do you need something more intelligent, i.e. that would prevent starvation?<br> <strong>A:</strong> A simple round robin type distribution would suffice, by starvation I assume you mean if there are no available sessions that callers become blocked waiting for releases. This isn't really applicable since the sessions can be shared by different callers. My goal is distribute the usage across multiple sessions as opposed to 1 single session.</p> <p>I believe this is probably a divergence from a normal usage of an object pool which is why I originally left this part out and planned just to adapt the pattern to allow sharing of objects as opposed to allowing a starvation situation to ever occur.</p> <p><strong>Q:</strong> What about things like priorities, lazy vs. eager loading, etc.?<br> <strong>A:</strong> There is no prioritization involved, for simplicity's sake just assume that I would create the pool of available objects at the creation of the pool itself.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChris Marisic
    1. USChris Marisic
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    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. POC# Object Pooling Pattern implementation
      1. USChris Marisic
      1. VTBountyStart
    2. VO
      singulars
      1. POC# Object Pooling Pattern implementation
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POC# Object Pooling Pattern implementation
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you tell us a bit about your requirements? Not all pools are created equal. Are the objects expensive to create? Will they be acquired/released very frequently? Will a simple first-come-first-serve suffice or do you need something more intelligent, i.e. that would prevent starvation? What about things like priorities, lazy vs. eager loading, etc.? Anything you can add would help us (or at least me) to come up with a more thorough answer.
      singulars
      1. POC# Object Pooling Pattern implementation
      1. USAaronaught
    2. COChris - just looking at your 2nd and 3rd paragraphs, and wondering whether these sessions should really be kept alive indefinitely? It sounds like that's what your service provider doesn't like (long-running sessions), and so you might be looking for a pool implementation that spins up new sessions as necessary and shuts them down when not in use (after some specified period). This can be done, but is a little more complicated, so I'd like to confirm.
      singulars
      1. POC# Object Pooling Pattern implementation
      1. USAaronaught
    3. COI'm not sure if I need that robust of a solution or not yet as my solution is merely hypothetical. It's possible that my service provider is just lying to me and that their service is over sold and have merely found an excuse for a way to blame the user.
      singulars
      1. POC# Object Pooling Pattern implementation
      1. USChris Marisic
 

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