nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

MediaBin search taking 60+ seconds for a folder with 13 assets

Bill Klish

MediaBin 4.5.3
SQL Server 2000 SP4

We are attempting to run a complicated search query with 12 criteria against a single directory (has 13 assets in it) with 2 sub directories (one has 1 asset, the other has 11).

It is taking 60+ seconds for the query to return 0 assets and I am not seeing anything unusual in the MediaBin logs.

We attempted this in our custom Java app and the web client and see similar results.

We do have a lot of deadlocks happening, not recently, but yesterday there were 47 on the LRUCache tables that failed and said to re-run, which is not a good sign. However, this works for less complicated search queries without an issue.

Query looks like this:
CTYHOCN (Must be in all caps) is exactly BXHBRHN AND
Brand.com Submission Status is Completed / On Brand.com AND
Asset Category exists AND
Asset Category is not n/a AND
Hotel Name exists AND
Image Usage Rights is Internet (Brand.com) AND
Brand.com Pages is dining_managers_reception OR
Brand.com Pages is dining_cooked-to-order_breakfast OR
Brand.com Pages is dining_on-the-house_hot_breakfast OR
Brand.com Pages is dining_evening_room_service OR
Brand.com Pages is dining_welcome_home_reception OR
Brand.com Pages is dining_suite_start_hot_breakfast

Find more posts tagged with

Comments

lyman

Check the net.log for the running time of the FindRequest. If that seems to be unusually long we can dig into the DB.log to see if the server or database is to blame.

Cheers,

Lyman Hurd

kg_brian

03/11/08 10:45:04 ConnId:431 Session#:1 Processed request CFindRequest. Took 20157ms

03/11/08 10:46:28 ConnId:432 Session#:1 Processed request CFindRequest. Took 14953ms

Little better than last week, but 15-20 seconds for a search seems a little long still...

Migrateduser

Hey Brian,

We had a very similar issue and we found (thanks to support) that our database was not reindexing correctly. Also we found that when the MediaBin Enterprise Manager HouseKeeping maintenace was running, it was causing all kinds of deadlocks and data collisions. We turned all that off and setup our own SQL Server scripts on the backend.

You might want to confirm that you db is being reindexed correctly?

Stacy

finalprotocolviewer.bmp

kg_brian

How do I tell if the reindex is "correct"

Migrateduser

Hey Brian,

Here are some good articles to read.

http://sqlserver-qa.net/blogs/perftune/archive/2008/01/21/3208.aspx

http://www.sql-server-performance.com/articles/per/detect_fragmentation_sql2000_sql2005_p1.aspx

Hope you find this helpful.

Stacy

lyman

There was a patch recently I believe that addressed MediaBin's automatic reindex. If you open a case with support they can figure out if you need to apply it.

Cheers,

Lyman Hurd

kg_brian

There was a patch recently I believe that addressed MediaBin's automatic reindex. If you open a case with support they can figure out if you need to apply it.

Cheers,

Lyman Hurd

Is this patch for 4.5.3?

Bill Klish

I don't see any patches relating to this available for 4.5.3. Lyman, are you speaking about another version of MediaBin?

We opened a support case to track this issue, and validated that the 12 reindexing procedures ran successfully according to the logs.

This issue still happens. I have had a separate support case open for this issue that I have heard nothing back on in over a week. If I hear anything back will post the response back out here.

Migrateduser

Hey Brian,

(Disclaimer: I don't know if you have worked with iwov with patches, they seem to have a screwed up way of patching and have multiple code trees. So, be aware that if you install one patch, it might blow away the configuration for another patch at that point iwov engineering has to make a "roll-up" patch for you that includes both patches. Screwy.)

When I saw this mail, I contacted support for my own selfishness as I wanted that same patch. I rec'd the following message from Jayashree...

Patch ID 1875 : MediaBin 4.6.0 for Windows

12/20/2007 Ref: 75288 Recommended

Directions: readme/install directions

Source: download (810KB)

Summary: Please see the Readme file

Note: This patch also contains patch#75289

I am using 4.5.3 and not 4.6.0 which (I got from the support web site) is the following. The part part for us is that this does blow away one of our patches and they are currently making a roll-up patch for us now. Jeez...

Patch ID 1867 : MediaBin 4.5.3 for Windows
11/20/2007	Ref: 75288, 5858	Recommended
Directions:	readme/install directions
Source:	download (1.38MB)
Summary:	Please see Readme
Note:	This patch affects all MediaBin clients and server applications

lyman

Sorry for the delay. I have been out on vacation for a week.

I did some further checking and the reason that there is no 4.5.3 version of the patch I had in mind was that this particular issue was specific to 4.6.

However, if you open a support case there may be some ways to help improve performance. Next next level of drill down I know they will want to see is db.log (make sure that is active). This log fills up quickly and so it is useful to copy it immediately after running the search to avoid truncation.

Cheers,

Lyman

Bill Klish

I worked with support and we determined the cause of the issue was all of the OR statements. We replaced them all with a StartsWith clause and the query went from 82 seconds to less than a second.

What tripped us up was the fact that Startswith was not a metadata operation choice in the UI or by looking at the available operators using the web services API. The good news is, even though it is not surfaced in the UIs or the API, you can still use it if you know what the operator is.

It would be good to make the list of search operators some sort of enumeration exposed in the web services so people don't need to know it is OpExists, StartsWith, etc. We had to write a little program and dump out all of the operators for all searchable metadata to find the right operator names. If this already exists let me know where, but we didn't see it.

lyman

There was a patch recently I believe that addressed MediaBin's automatic reindex. If you open a case with support they can figure out if you need to apply it.

Cheers,

Lyman Hurd

I apologize. On further checking this fix was 4.6 specific and did not affect 4.5.3 which did not demonstrate the behavior in question...

Cheers,

Lyman Hurd