RampUp | NET library providing performant low-alloc algorithms | Learning library

Asked a similar question before, but I marked it answered, and I have other information.

Here is the structure:

The following snapshot shows the file structure:

When I run on Gitlab CI, here is what I am seeing:

Why is this error occurring when Gitlab runs it but not when I run locally?

Here is my .gitlab-ci.yml file.

Note that this had been working before.
I recently made win_perf_counters a Git submodule instead of being an actual subdirectory. (Again, it works locally.)

Load Runner controller : After Rampup is attained we see a dip in Vusers and then target Vusers are attained. This causes load to fluctuate and response time been affected. What can I look into next?

In screenshot below we can see after target of 1800 users is attained at 00.50 again Vusers falls back to 1500 users and then ramped up to 1800. This happens in most of the runs from Load Runner.

This is based on the answer in JMeter & Gitlab: How to Install & SQLServer JDBC Driver?.

In short, the debug output below shows that the appropriate JAR and DLL are in the Java-path on the Docker image, yet I am seeing the following error in the JMeter output:

• "DBCP DataSource configured without a 'password'" mssql
• "DBCP DataSource configured without a 'user'" mssql

The image uses JMeter 5.4.2 ("latest").

The JDBC driver files I am using are:

• mssql-jdbc_auth-9.4.1.x86.dll
• mssql-jdbc-9.4.1.jre8.jar

So is it a compatibility issue?

I have JMeter 5.4.1 installed on my computer, and the test plan works fine using the local application.

Here is the output from the Gitlab job:

I have an issue with a Jmeter scenario where my dashboard report is getting a start time of Start Time "1/1/70, 12:00 AM"

The end time is working fine End Time "12/11/21, 10:04 PM"

In the same script, If I disable the thread group hitting this issue and run another thread group, the start time is ok. This leads me to think it's a problem with the timing in this particular thread group rather than a problem with my JM props.

I am attempting to simulate long (1 hour +) websocket sessions with a start/pingpong/end.

• Runtime controller with a sub loop controller running the websocket ping/pong in the middle.

• The ping/pong uses a runtime controller where duration = rampup + full load time.

• The pingpong loop controller runs every 60 sec for the duration of the thread rampup + full load.

• The overall threadgroup duration is (rampup x 2) + full load.

As far as I can tell all of this adds up to long running threads doing the needed txns, while keeping open websocket connections, and running as expected.

I set DEBUG for Report logging and nothing unusual is jumping out at me as a cause. (Those relevant logs below)

The only Report related JMeter props that I am customizing at runtime or otherwise are the following:

I have been programming an API using Django and djangorestframework for deployment in Google App Engine. The API is basically a package registry, so you can create, update, get, and delete packages with the API.

All the endpoints seem to work except for one. The only endpoint that doesn't work is one that display a paginated list of all packages in the online registry.

All the endpoints are working, but for some reason, when I hit the specific endpoint '/packages/', GCP gives me the error

Hi Need clarification for python variable stored as wrong value , here is code :

I installed JMeter 5.3, created one thread group with 10/10/10 (users/rampup time/loop count), so I expect to get 100 requests executed total and see graph with one line which will show how long requests take, BUT I see that 300 requests were executed and my report dashboard looks like this:

I am completly new to zsh, come to it after discovering that macosx on catalina highly push to it. While I got a bit disoriented at first, I managed to rampup my knowledge of it, and so far I am about happy with it. Yet I bump into an issue that I can't solve with a trivial setopt, so may be one out there can help me.

The problem I got is with regular indexed arrays, like the following snippet