Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. Database connection pool thr application

Database connection pool thr application

Scheduled Pinned Locked Moved Web Development
questiondatabaseoracle
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    anishkannan
    wrote on last edited by
    #1

    Hi... In my web application, we are using oracle database. my question is connection pool based on web application. Our application end user around 500. for these which connection is better i) create new connection for every request of user. ii) single connection pool via singleton object of the class iii) session based connection pool ( each user has separate connection pool) which principle is using for web application? can please give suggestion or valuable link to me --Thanks

    R C 2 Replies Last reply
    0
    • A anishkannan

      Hi... In my web application, we are using oracle database. my question is connection pool based on web application. Our application end user around 500. for these which connection is better i) create new connection for every request of user. ii) single connection pool via singleton object of the class iii) session based connection pool ( each user has separate connection pool) which principle is using for web application? can please give suggestion or valuable link to me --Thanks

      R Offline
      R Offline
      R Giskard Reventlov
      wrote on last edited by
      #2

      This might be useful: ADO.NET Connection Pooling at a Glance[^].

      "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me

      1 Reply Last reply
      0
      • A anishkannan

        Hi... In my web application, we are using oracle database. my question is connection pool based on web application. Our application end user around 500. for these which connection is better i) create new connection for every request of user. ii) single connection pool via singleton object of the class iii) session based connection pool ( each user has separate connection pool) which principle is using for web application? can please give suggestion or valuable link to me --Thanks

        C Offline
        C Offline
        creditmesh
        wrote on last edited by
        #3

        If you get a lot of people connecting. Specfic pool for specfic guy is not an good thing because it whould cost too expensive resource usage. The ideal solution is one link conducting many database links. In my project. One or serveral thread are only conducting database connecting and sql processsing. When finished the sql it will send data to others.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups