Hi,
I updated to the May 26th snapshot and one batch process that used to take 45 seconds now takes more than 25 minutes to run.
A couple of months ago we had that issue, we were asked if we were updating files that use namespaces... and then that lead to a new snapshot. I never got the details of the issue, but this has a very familiar feel.
Could the namespace processing issue be back?
Never mind, I found an issue on my side.
On Mon, May 26, 2014 at 12:12 PM, France Baril <france.baril@architextus.com
wrote:
Hi,
I updated to the May 26th snapshot and one batch process that used to take 45 seconds now takes more than 25 minutes to run.
A couple of months ago we had that issue, we were asked if we were updating files that use namespaces... and then that lead to a new snapshot. I never got the details of the issue, but this has a very familiar feel.
Could the namespace processing issue be back?
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com (514) 572-0341
Hi France,
Could the namespace processing issue be back?
The namespace issue should be fixed. Did you encounter the issues with a new database, or could it be that the contents of the database were created with a version before the namespace fix? In the latter case, you could try to call OPTIMIZE ALL and see if that helps.
Best, Christian
On Mon, May 26, 2014 at 6:12 PM, France Baril france.baril@architextus.com wrote:
Hi,
I updated to the May 26th snapshot and one batch process that used to take 45 seconds now takes more than 25 minutes to run.
A couple of months ago we had that issue, we were asked if we were updating files that use namespaces... and then that lead to a new snapshot. I never got the details of the issue, but this has a very familiar feel.
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com (514) 572-0341
Yope, issue was on my side. It's resolved. Thanks!
On Tue, May 27, 2014 at 6:23 PM, Christian Grün christian.gruen@gmail.comwrote:
Hi France,
Could the namespace processing issue be back?
The namespace issue should be fixed. Did you encounter the issues with a new database, or could it be that the contents of the database were created with a version before the namespace fix? In the latter case, you could try to call OPTIMIZE ALL and see if that helps.
Best, Christian
On Mon, May 26, 2014 at 6:12 PM, France Baril france.baril@architextus.com wrote:
Hi,
I updated to the May 26th snapshot and one batch process that used to
take
45 seconds now takes more than 25 minutes to run.
A couple of months ago we had that issue, we were asked if we were
updating
files that use namespaces... and then that lead to a new snapshot. I
never
got the details of the issue, but this has a very familiar feel.
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com (514) 572-0341
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
France Baril