XMLWordPrintable

Details

    • New Feature
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • Non blocking API
    • None

    Description

      The current async implementation using _start/_cont API requires applications to manually handle I/O waiting using platform-specific code (epoll/poll/select). This creates unnecessary complexity and code duplication across applications. Benchmark results show that the async API exceed synchronous performance but only when properly optimized.

      Current Problems

      Runtime Mode Switching is Unnecessary

      MYSQL_OPT_NONBLOCK can be set/changed at any time. In practice, applications never switch between sync/async modes at runtime
      This flexibility prevents optimization opportunities
      Proposed: Make async mode a connection-time decision only, enabling better optimizations (optimization will even be good for standard sync version)

      SSL/TLS SChannel Not Implemented

      this is handled by CONC-806

      Attachments

        Activity

          People

            georg Georg Richter
            diego dupin Diego Dupin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.