NScan response times

We also use a dedicated network for our scanners.

--Tom

On Tue, Mar 17, 2015 at 3:16 PM, N-Scan wrote:
We also found that adding a dedicated WiFi access point, that the general public cannot connect to, helped with some slowness that we saw with our MC55 scanners. We entered the MAC addresses of the scanner devices to the access point’s connection table, so only those devices can connect to the dedicated access point, and we have not seen the slowness since then.


Penny Tabor
Director of Technology
Midland Center for the Arts
Midland, MI 48640
(989) 631-5930 X 1207
[/Community/cfs-filesystemfile.ashx/__key/CommunityServer.MailGateway.MailRoom.ForumsHandler/d72d7fd4682549419f13885e08caaef8/image003.jpg]




From: N-Scan [mailto:groups-n-scan@tessituranetwork.com] On Behalf Of Caryl Jones
Sent: Tuesday, March 17, 2015 2:58 PM
To: Tabor, Penny
Subject: Re: [N-Scan] NScan response times


Hi Paul,

We have up to 24 scanners working concurrently in our building and we haven't seen any slow down at all when using multiple scanners.

The only time we ever get any response issues is when there is an issue with the WIFI connection e.g. the Steward has moved out of range of the WIFI.

One thing that we did do was make sure that the scanners were using a hidden WIFI account, and locked down by device what could attach to the WIFI, so that during an incoming customers mobile phones were finding and trying to attach to the WIFI. This might be something to look at, as it may be other devices connecting that are causing the issues.

Caryl
From: Paul Thompson >
Sent: 3/17/2015 10:08:28 AM

Hi everyone,

I'm new to the forum, still pretty new to the role in fact, just 4 months now!

Since I started, NScan has been at the top of my to-fix list. We're using the Motorola MC65b for hardware with both Tessitura and print-at-home tickets. I've identified that we may have difficulties with our WiFi network and we're addressing that through capital investment but, even when the WiFi is up, the NScan system doesn't respond in a particularly timely manner when there are lots of tickets being scanned concurrently. Has anyone else found this? It can be fine with just one or two scanners but once we have 4 or 6 on the go it really slows down.

I've put a couple of suggestions in to the development team that we
a) separate the database 'write' elements of the code to some separate procedure and
b) ensure the stored procedure is able to be called by more than one process at a time as my diagnosis seems to suggest we're seeing queuing of requests which is leading to a considerable slowdown in processing.

So far they are still pondering these ideas so I wondered what the community's experience is please and if you have any suggestions for tweaks we could employ to speed things along?

Thanks everyone, look forward to hearing from you!
Kind regards,

Paul Thompson
IT Manager
Mayflower Theatre
Paul.Thompson@Mayflower.org.uk

We also use a dedicated network for our scanners.

--Tom

On Tue, Mar 17, 2015 at 3:16 PM, N-Scan wrote:
We also found that adding a dedicated WiFi access point, that the general public cannot connect to, helped with some slowness that we saw with our MC55 scanners. We entered the MAC addresses of the scanner devices to the access point’s connection table, so only those devices can connect to the dedicated access point, and we have not seen the slowness since then.


Penny Tabor
Director of Technology
Midland Center for the Arts
Midland, MI 48640
(989) 631-5930 X 1207
[/Community/cfs-filesystemfile.ashx/__key/CommunityServer.MailGateway.MailRoom.ForumsHandler/d72d7fd4682549419f13885e08caaef8/image003.jpg]




From: N-Scan [mailto:groups-n-scan@tessituranetwork.com] On Behalf Of Caryl Jones
Sent: Tuesday, March 17, 2015 2:58 PM
To: Tabor, Penny
Subject: Re: [N-Scan] NScan response times


Hi Paul,

We have up to 24 scanners working concurrently in our building and we haven't seen any slow down at all when using multiple scanners.

The only time we ever get any response issues is when there is an issue with the WIFI connection e.g. the Steward has moved out of range of the WIFI.

One thing that we did do was make sure that the scanners were using a hidden WIFI account, and locked down by device what could attach to the WIFI, so that during an incoming customers mobile phones were finding and trying to attach to the WIFI. This might be something to look at, as it may be other devices connecting that are causing the issues.

Caryl
From: Paul Thompson >
Sent: 3/17/2015 10:08:28 AM

Hi everyone,

I'm new to the forum, still pretty new to the role in fact, just 4 months now!

Since I started, NScan has been at the top of my to-fix list. We're using the Motorola MC65b for hardware with both Tessitura and print-at-home tickets. I've identified that we may have difficulties with our WiFi network and we're addressing that through capital investment but, even when the WiFi is up, the NScan system doesn't respond in a particularly timely manner when there are lots of tickets being scanned concurrently. Has anyone else found this? It can be fine with just one or two scanners but once we have 4 or 6 on the go it really slows down.

I've put a couple of suggestions in to the development team that we
a) separate the database 'write' elements of the code to some separate procedure and
b) ensure the stored procedure is able to be called by more than one process at a time as my diagnosis seems to suggest we're seeing queuing of requests which is leading to a considerable slowdown in processing.

So far they are still pondering these ideas so I wondered what the community's experience is please and if you have any suggestions for tweaks we could employ to speed things along?

Thanks everyone, look forward to hearing from you!
Kind regards,

Paul Thompson
IT Manager
Mayflower Theatre
Paul.Thompson@Mayflower.org.uk