<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:21:20 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[DRIVERS-361] Atlas Users Experience Poor Performance on AWS Lambda </title>
                <link>https://jira.mongodb.org/browse/DRIVERS-361</link>
                <project id="10980" key="DRIVERS">Drivers</project>
                    <description>&lt;p&gt;MongoDB and Atlas users are experiencing poor performance when using MongoDB from AWS Lambda Functions. This is likely due to a current inability to persist connection pools between execution of Lambda functions, thus a connection pool must be created for each execution.&lt;/p&gt;

&lt;p&gt;I imagine Lambda provides some type of execution context which users can persist mongoclient instances to be referenced for subsequent operations. The drivers may need to be modified to make use of this persistent context. &lt;/p&gt;
</description>
                <environment></environment>
        <key id="365117">DRIVERS-361</key>
            <summary>Atlas Users Experience Poor Performance on AWS Lambda </summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="13202">Works as Designed</resolution>
                                        <assignee username="matt.broadstone@mongodb.com">Matt Broadstone</assignee>
                                    <reporter username="bryan.reinero">Bryan Reinero</reporter>
                        <labels>
                    </labels>
                <created>Wed, 15 Mar 2017 19:40:19 +0000</created>
                <updated>Fri, 27 Oct 2023 12:27:28 +0000</updated>
                            <resolved>Fri, 5 Jan 2018 18:28:48 +0000</resolved>
                                                                            <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="1766401" author="matt.broadstone" created="Fri, 5 Jan 2018 18:28:48 +0000"  >&lt;p&gt;This can be (and has been) solved through documentation, no work needed for drivers.&lt;/p&gt;</comment>
                            <comment id="1525231" author="raphael.londner" created="Wed, 15 Mar 2017 21:57:42 +0000"  >&lt;p&gt;Lambda functions are supposed to be stateless but in reality, a container running a specific Lambda function might be reused for close, consecutive function calls. This might allow the code to reuse a db connection that was previously opened (provided it hasn&apos;t been closed). &lt;/p&gt;

&lt;p&gt;Heard from &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=sigfrido.narvaez&quot; class=&quot;user-hover&quot; rel=&quot;sigfrido.narvaez&quot;&gt;sigfrido.narvaez&lt;/a&gt; that Python Lambda functions would allow re-use of the database connection across calls (provided that connection has not been closed in a previous function call).&lt;/p&gt;

&lt;p&gt;With Node.js however, it looks like the db connection must be closed after being used or the Lambda function times out, which prevents it from being re-used on subsequent calls.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                                        </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                            <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10257" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Documentation Changes</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="11861"><![CDATA[Not Needed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hswrzb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>