We are happy to announce the Moose Suite version 4.6:
http://moosetechnology.org/download
What is new:
• New editors for scripting browsers and visualizations
• Improved Glamour browser building engine
• Improved EyeSee charting engine
• Improved FAMIX API
• Improved FAMIX to support Java and C++
• Improved external importers to support Java and C++
A list of issues addressed in this release can be found at:
http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%…
Have fun,
The Moose Team
Hi,
Sorry for the late reply, and thanks everyone for the suggestions.
I did not provide much details because I am new to this domain and I wanted to see from the reactions if maybe I am not missing some relevant direction.
We are trying to measure how an Oracle database can cope with an increase in usage (basically, there will be more users for the application). We are basing our analysis on typical SQL statements coming from the application. We are currently doing load testing by:
- recording sql statements from some use cases that are considered to be important
- generalizing them by replacing actual values with generic variables
- providing meaningful values for the generic variables
- replaying them against the database from several client machines
- consuming the first record from the responses
- reporting the timing of the statements
- recording the CPU, memory and I/O load of the server
However, I am interested in pitfalls, and in the way people interpret the results given that it is hard to determine what is a typical usage in terms of what statements to trigger and at what delays.
Cheers,
Doru
On 5 Feb 2012, at 19:02, Philippe Marschall wrote:
> On 03.02.2012 16:11, Tudor Girba wrote:
>> Hi,
>>
>> Do you happen to know methods to approach the problem of testing the
>> capacity of an application to work with an SQL database?
>
> Which capacity?
>
>> In particular, I am interested in simulating concurrent requests
>> towards this database that would resemble the interaction coming from
>> the application.
>
> What are you trying to measure?
>
> Well you know that benchmarking is hard, don't you? I see two possible ways. First recording the SQL statements and then replaying them (have fun with bind parameters). Second just running the application itself.
>
> Oh yeah, Oracle has a tool named RAT, no idea what the marketing department though there. Maybe you can play similar tricks with PITR in PostgreS.
>
> Cheers
> Philippe
>
>
--
www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 775 by marcmoo...(a)gmail.com: Pane partially clipped
http://code.google.com/p/moose-technology/issues/detail?id=775
Hello
I have some small problem in Glamour. When I execute following in a
Workspace
| browser |
browser := GLMTabulator new.
browser row: #menuBar size: 25. "Bottom Part get hidden because of this"
browser row: [ :r1 |
r1
column: [ :c|
c
row: [:r |
r
column: #one;
column: #two
] span: 2;
row: #three.
]].
browser transmit to: #one; andShow: [:a |
a title: 'One'.
a list ].
browser transmit to: #two; andShow: [:a |
a title: 'Two'.
a list ].
browser transmit to: #three; andShow: [:a |
a title: 'Three'.
a list "title: 'List'" ].
browser openOn: (1 to: 10)
the bottom part of the third pane is partially hidden. Do I something wrong?
(A hacky workaround is to simplay add an additional row with size 25 --
which then is invisible)
(See attached picture)
Tested in Pharo 1.1 - 1.3
Marc
Please fill in the labels with the following information:
* Type-Defect
* Component-Glamour
Attachments:
hidden.png 18.5 KB
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-EyeSee
New issue 759 by tu...(a)tudorgirba.com: EyeSee window should provide export
options
http://code.google.com/p/moose-technology/issues/detail?id=759
We should be able to easily export a chart to file.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 751 by stephane...(a)gmail.com: Problem with isPrime
http://code.google.com/p/moose-technology/issues/detail?id=751
Describe the problem: what do you get? what do you expect?
How to reproduce the problem: step by step if necessary
Additional information: platform, context which may impact the problem
Please fill in the labels with the following information:
* Type-Defect, Type-Enhancement, Type-Engineering, Type-Review, Type-Other
* Component-XXX
Hi,
As there is not much activity around Moose, there is hardly any point to wait for releasing 4.6.
I will do it tomorrow. If you have objections, please raise them until then.
Cheers,
Doru
--
www.tudorgirba.com
"Reasonable is what we are accustomed with."
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 750 by usman.bh...(a)gmail.com:
GLMTextModel(Object)>>doesNotUnderstand: #highlightSmalltalk:
http://code.google.com/p/moose-technology/issues/detail?id=750
In Menssana, when clicking on various reports, we get this error.
- Import a model in moose
- Launch detailed dashboard in menssana -> top ten lint rules -> browse
classes and then we get this error.
I may be missing some extensions of glamour in my image?
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 743 by usman.bh...(a)gmail.com: This is strange that we have to
systematically specify the class of the importer
http://code.google.com/p/moose-technology/issues/detail?id=743
a typical sript to import a model is
MooseSqueakClassPackageImporterTask new
importerClass: SmalltalkImporter;
model: model;
addFromPackageNamed: #'Moose-TestResources-LAN';
run;
yourself
But it is rare that we should change the importerClass (it was useful when
we had to import FAMIX2 and FAMIX3 side by side).
I suggest that we introduce a default and that we initialize the
importerClass to SmalltalkImporter.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Platform-Pharo Component-EyeSee
New issue 738 by alexandr...(a)gmail.com: bugs in EyeSee
http://code.google.com/p/moose-technology/issues/detail?id=738
I played with the matrix in EyeSee in a Pharo image. I found some problems:
- #new:withAll: and #new: seems to raise an emergency debugger, whatever
the value we provide
- Many references are made that do not belong to EyeSee. For example
#zero that refers to MalMatrixCoercion
I also found other problems (e.g., hash).
I added some tests for those.
I produced version 0.9.2
Cheers,
Alexandre
Status: New
Owner: ----
CC: georgega...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-ExternalTools
New issue 730 by tu...(a)tudorgirba.com: inFamix should create namespaces
without path information
http://code.google.com/p/moose-technology/issues/detail?id=730
Currently, inFamix is exporting namespaces with names containing path
information like src/com::example. It should be only com::example.