Skip to main content

Load testing and MyEd

One disappointment in the run-up to the new semester was that the upgrade to our university portal failed its load test.  In other words, when we tried running ithe new version with automated tests that simulated the number of staff and students who would be using it in real life, the time it took to display the login screen was too long to be acceptable. Hence we decided to delay the upgrade.

The good news is that we have found the cause of the problem and we have a fix. So we should be able to give staff and students the enhanced version sometime around the middle of the semester. 

An underlying point is that these tests are an important part of our quality assurance process. The portal is used every day by thousands of people and the poor performance we were seeing would have significantly affected their work.  We can take some satisfaction from the fact that we did catch the problem before putting the new system live.

Ideally we would have run the load tests earlier so that we would have had time to fix the problems and still deploy the new version on schedule.  Unfortunately this was not the first stumbling block that we encountered with this upgrade.  Some projects are like that.  It's not unusual to find some problems on any project - in fact it would be most unusual to have none at all - but there are some projects that seem to attract more than their fair share.

We will have a review of the project when is finally completed, with the aim of looking for ways of avoiding problems in future projects.  For example, one issue that we have already noted is that the way the portal technology handles groups of users is changing, and this change does seem to be related to the performance problems we were seeing.  This suggests that we will have to change our implementation to match the new way of working, next time we upgrade this technology.



Comments

Popular posts from this blog

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Service Excellence, Digital Transformation and Enterprise Architecture

Our University Secretary has sponsored a major review of the University’s administrative processes, coining the banner “Service Excellence”.  The aim is to look at the services we provide to staff and students with a fresh eye, making them more effective, more efficient, and focussed on the user rather than administrative convenience.

Our CIO is sponsoring a similar programme called “Digital Transformation”. This will replace old paper-based processes, starting with the question of what would processes look like if we designed them afresh for the modern connected world.  The aim is to make processes that are more focussed on the user and hence more effective and efficient.

Both of these ambitious programmes will need an effective enterprise architecture, if they are to succeed.  Digital Transformation is intrinsically about using opportunities provided by new technology to improve services and, as such, it requires effective technology services to make data available when needed, to pro…

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:


I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…