Time taken to go into test

aware_support

Try MySQL 5.5

pbrad

Hi,
Here are my test results:

Windows 7
MySQL 5.5.16
xampp 2.5
AwareIM version 5.7 build 1706
Memory Settings: AwareIM 512mb, Tomcat 256mb, jboss 256mb, config tool 1024mb

Problem BSV:
BSV exported size:
Time to go into test mode without checking integrity: 9 minutes 41 seconds
Time to go into test mode with checking integrity: 9 minutes 50 seconds

Problem BSV imported into a blank business space:
Time to go into test mode without checking integrity: 12 seconds

Please let me know if you need any other info.

Thanks,
Pete

RLJB

Ubuntu 12.04 LTS
MySQL 5.5.32
AwareIM version 5.7 build 1701
Memory: AwareIM 2048mb, Tomcat 2048mb, jboss 2048mb, config tool 2048mb

Also note when going into test, it seems to take a LONG time executing the command:

DELETE FROM DOMAINVERSIONS WHERE DNAME=? AND VERSIONSTR=?

And the system load goes to 98%

See screenshot from MySQL Workbench:

RLJB

http://imageshack.us/photo/my-images/10/tw5i.png/

Gabbitas

PostPosted: Thu Oct 31, 2013 7:06 am Post subject:
Try MySQL 5.5

My apologies, I said above that I was using MySQL 5.6 when in actual fact I'm using MySQL 5.5.34

Thanks

ACDC

I had the exact same problem and was able to resolve the problem by deleting all my BSV versions by systematically deleting each one until I was left with my current BSV. I did this on each application in the configurator.

Also, after deleting I inspected the database and found some entries that should have been deleted. I suspect these entries were not deleted due to some issue with awareim or maybe had to do with a previous database restore some time back that inadvertently restored things that were originally deleted in the configurator. Anyway after getting rid of these by a direct edit to the database things were back to normal

Mysql 5.5
AIM 5.7
Windows Server 2008 R2 standard

RLJB

Great advice ACDC. Problem solved:

We had over 5600 rows in the Domain Versions table of the database. I suspect many of these came from an old dev server and we just copied across the DB.

We systematically went through each business space, made new major versions, then deleted all old versions and dumped all the old rows from the MySQL table. Our table size went from about 2.6 GB to about 100MB.

We are now into test in about 25 seconds, it's 4 days in and it's still about 25 seconds.

Powerm

ACDC wrote
Also, after deleting I inspected the database and found some entries that should have been deleted. I suspect these entries were not deleted due to some issue with awareim

This is true, when you delta a bsv all Tables are not delete on the database. You should always have a clean server based AwareIM and an other one in a testing mahine. This is a fact, more bsv's and versions of the bsv you will have , slower will be your system.

Gabbitas

I have now deleted all obsolete versions of all business spaces and have only one business space in test mode and no other versions loaded. I am currently experiencing time to go into test of around 10 mins. This is very frustrating as it is prolonging progress. The time to test just seems to get longer and longer.

I have taken a look at the domainversions table using MySQL Workbench (It took almost 4 mins just to load and view the table in workbench!) There is nearly 1000 rows in the basdbtest database and only 18 in basdb. It looks as if the old basdb rows get deleted when a version is published but in the basdbtest database they are never deleted and it means for a very large table.

I would like to delete any unnecessary rows in the basdbtest domainversions table but I'm a bit worried that I will screw things up. I don't understand how I can tell which rows are obsolete and which are in use. Can anybody point me in the right direction please?

Support have you got any further ideas about why we might be experiencing these long test times? Is deleting the rows from domainversions a good idea or should aware be doing it automatically?

Thanks

Gabbitas

I'm still getting this problem. Its happening in all my BSVs. The more times I put them into test the longer it takes each time. Even on very small BSVs the result is the same.

Has anyone found a solution? The only work around I have, as sugested by PBrad, is to create a new BSV from time to time and import from the slow to test BSV. When I do this the time to test instantly comes down from 10mins or more to less than 1 min on small BSVs then the whole process starts again - 2 weeks later after many times into and out of test it becomes slow so I have to create a new BSV.

Thanks

ACDC

The simple solution here is to do an export of each BSV, then do an sql dump of your BASDB. You now have a full backup of your system

Delete BASDB and BASDBTest

Re install awareim

Recreate each BSV and import each version BSV and publish each one

Restore BASDB from the sql dump taking care not to restore any system tables - only tables related to your application data must be imported

Before proceeding inspect the basdb with a suitable database editor and check to see if there are any tables that should not be there ie Maybe from a previous demo bsv or an old bsv that you deleted and the deletion did not carry through to basdb. - delete these

You now will have a clean system behaving normally

Also, make sure you have more than one backup and VERY IMPORTANT if you have never done this before,, practice by doing a simulation on another machine using a trial version with your live data. This will make sure you don't loose data and get yourself into a mess when you do the real thing

« Previous Page